templates: bump payload and next.js versions#16229
Merged
Conversation
AlessioGr
changed the title
PatrikKozak
approved these changes
Apr 9, 2026
Contributor
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖
Largest pathsThese visualization shows top 20 largest paths in the bundle.Meta file: packages/next/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_shared.json, Out file: esbuild/exports/shared.js
Meta file: packages/richtext-lexical/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_shared.json, Out file: esbuild/exports/shared_optimized/index.js
DetailsNext to the size is how much the size has increased or decreased compared with the base branch of this PR.
|
Contributor
|
🚀 This is included in version v3.83.0 |
paulpopus
pushed a commit
that referenced
this pull request
Apr 17, 2026
### What? Bump the plugin template's pinned Payload package versions from `3.37.0` to `3.82.1` and add it to `generate-template-variations.ts` so future releases bump it automatically. ### Why? Audit against the current Payload version (`3.82.1`): | Template | Payload version | Status | |---|---|---| | `blank`, `ecommerce`, `website` | `workspace:*` | ✅ auto-bumped | | `with-cloudflare-d1`, `with-postgres`, `with-vercel-*` | `3.82.1` | ✅ bumped via release workflow / manual PRs | | `plugin` | `3.37.0` | ❌ stale (~45 patches behind) | The plugin template is not a standard app-template variation, so `generate-template-variations.ts` skipped it entirely. The post-release workflow therefore never touched it, and the recent manual bump PRs (#16212, #16229) only covered app templates. ### How? 1. `templates/plugin/package.json` — bump `payload` + `@payloadcms/*` devDeps from `3.37.0` → `3.82.1`, bump `@payloadcms/eslint-config` from `3.9.0` → `3.28.0`, bump `peerDependencies.payload` from `^3.37.0` → `^3.82.1`. 2. `tools/scripts/src/generate-template-variations.ts`: - Allow `--template plugin` through the filter (plugin isn't a variation entry). - After the main loop, call a new `bumpPluginTemplate()` helper which resolves the latest `payload` version from npm and reuses `bumpPackageJson`. - Extend `bumpPackageJson` to also bump `peerDependencies` entries, writing `^<version>` so plugin consumers can install compatible patch/minor updates (exact pins would be too strict for a peer dep). Verified locally with `pnpm script:gen-templates --template plugin` — picked up the latest npm version (`3.83.0`), bumped devDeps, wrote `^3.83.0` to peer deps, and preserved `@payloadcms/eslint-config` via the existing `DO_NOT_BUMP` list.
milamer
pushed a commit
to milamer/payload
that referenced
this pull request
Apr 20, 2026
- Bumps payload version in templates from 3.82.0 to 3.82.1 - Bumps Next.js version in monorepo and templates from 16.2.2 to 16.2.3
milamer
pushed a commit
to milamer/payload
that referenced
this pull request
Apr 20, 2026
…#16305) ### What? Bump the plugin template's pinned Payload package versions from `3.37.0` to `3.82.1` and add it to `generate-template-variations.ts` so future releases bump it automatically. ### Why? Audit against the current Payload version (`3.82.1`): | Template | Payload version | Status | |---|---|---| | `blank`, `ecommerce`, `website` | `workspace:*` | ✅ auto-bumped | | `with-cloudflare-d1`, `with-postgres`, `with-vercel-*` | `3.82.1` | ✅ bumped via release workflow / manual PRs | | `plugin` | `3.37.0` | ❌ stale (~45 patches behind) | The plugin template is not a standard app-template variation, so `generate-template-variations.ts` skipped it entirely. The post-release workflow therefore never touched it, and the recent manual bump PRs (payloadcms#16212, payloadcms#16229) only covered app templates. ### How? 1. `templates/plugin/package.json` — bump `payload` + `@payloadcms/*` devDeps from `3.37.0` → `3.82.1`, bump `@payloadcms/eslint-config` from `3.9.0` → `3.28.0`, bump `peerDependencies.payload` from `^3.37.0` → `^3.82.1`. 2. `tools/scripts/src/generate-template-variations.ts`: - Allow `--template plugin` through the filter (plugin isn't a variation entry). - After the main loop, call a new `bumpPluginTemplate()` helper which resolves the latest `payload` version from npm and reuses `bumpPackageJson`. - Extend `bumpPackageJson` to also bump `peerDependencies` entries, writing `^<version>` so plugin consumers can install compatible patch/minor updates (exact pins would be too strict for a peer dep). Verified locally with `pnpm script:gen-templates --template plugin` — picked up the latest npm version (`3.83.0`), bumped devDeps, wrote `^3.83.0` to peer deps, and preserved `@payloadcms/eslint-config` via the existing `DO_NOT_BUMP` list.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.