fix(core): honor pnpm minimumReleaseAge config on pnpm 11 - #36335
Merged
Conversation
pnpm 11 changed `pnpm config list --json` to report configuration keys in camelCase (`minimumReleaseAge`), where pnpm 10 reported them kebab-case (`minimum-release-age`). The pnpm minimum-release-age reader only looked up the kebab-case keys, so on pnpm 11 every explicitly-set value (window, exclude, strict, ignore-missing-time) was dropped and the cooldown window fell back to the built-in 1440-minute default. `nx migrate` then reported 1440 regardless of the configured value. Read both the camelCase and kebab-case forms, preferring camelCase, so pnpm 11 config is honored while pnpm 10 keeps working. The existing pnpm 11 tests now mock pnpm 11's camelCase output; pnpm 10 tests keep the kebab-case form.
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for nx-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
View your CI Pipeline Execution ↗ for commit a74e5b6
☁️ Nx Cloud last updated this comment at |
FrozenPandaz
approved these changes
Jul 15, 2026
AgentEnder
pushed a commit
that referenced
this pull request
Jul 17, 2026
## Current Behavior pnpm 11 changed `pnpm config list --json` to report configuration keys in camelCase (`minimumReleaseAge`), where pnpm 10 reported them kebab-case (`minimum-release-age`). Nx's pnpm minimum-release-age reader only looked up the kebab-case keys, so on pnpm 11 every explicitly-set value (window, exclude, strict, ignore-missing-time) was ignored. The cooldown window fell back to the built-in 1440-minute default, so `nx migrate` reported 1440 no matter what `minimumReleaseAge` was set to in `pnpm-workspace.yaml`. Setting `NX_MIGRATE_USE_REGISTRY_RESOLUTION=false` was the only workaround. ## Expected Behavior The `minimumReleaseAge` configured in `pnpm-workspace.yaml` (or any other surface pnpm resolves) is honored on pnpm 11. The reader now reads both the camelCase (pnpm 11) and kebab-case (pnpm 10) forms, so pnpm 11 config is applied while pnpm 10 keeps working. ## Related Issue(s) Fixes #36330 <!-- polygraph-session-start --> --- [View session information ↗](https://app.trypolygraph.com/orgs/6a061dcb561c062131116eca/sessions/gh-36330-7fcd599a) <!-- polygraph-session-end -->
FrozenPandaz
pushed a commit
that referenced
this pull request
Jul 20, 2026
## Current Behavior pnpm 11 changed `pnpm config list --json` to report configuration keys in camelCase (`minimumReleaseAge`), where pnpm 10 reported them kebab-case (`minimum-release-age`). Nx's pnpm minimum-release-age reader only looked up the kebab-case keys, so on pnpm 11 every explicitly-set value (window, exclude, strict, ignore-missing-time) was ignored. The cooldown window fell back to the built-in 1440-minute default, so `nx migrate` reported 1440 no matter what `minimumReleaseAge` was set to in `pnpm-workspace.yaml`. Setting `NX_MIGRATE_USE_REGISTRY_RESOLUTION=false` was the only workaround. ## Expected Behavior The `minimumReleaseAge` configured in `pnpm-workspace.yaml` (or any other surface pnpm resolves) is honored on pnpm 11. The reader now reads both the camelCase (pnpm 11) and kebab-case (pnpm 10) forms, so pnpm 11 config is applied while pnpm 10 keeps working. ## Related Issue(s) Fixes #36330 <!-- polygraph-session-start --> --- [View session information ↗](https://app.trypolygraph.com/orgs/6a061dcb561c062131116eca/sessions/gh-36330-7fcd599a) <!-- polygraph-session-end --> (cherry picked from commit 7d9548b)
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.
Current Behavior
pnpm 11 changed
pnpm config list --jsonto report configuration keys in camelCase (minimumReleaseAge), where pnpm 10 reported them kebab-case (minimum-release-age). Nx's pnpm minimum-release-age reader only looked up the kebab-case keys, so on pnpm 11 every explicitly-set value (window, exclude, strict, ignore-missing-time) was ignored. The cooldown window fell back to the built-in 1440-minute default, sonx migratereported 1440 no matter whatminimumReleaseAgewas set to inpnpm-workspace.yaml. SettingNX_MIGRATE_USE_REGISTRY_RESOLUTION=falsewas the only workaround.Expected Behavior
The
minimumReleaseAgeconfigured inpnpm-workspace.yaml(or any other surface pnpm resolves) is honored on pnpm 11. The reader now reads both the camelCase (pnpm 11) and kebab-case (pnpm 10) forms, so pnpm 11 config is applied while pnpm 10 keeps working.Related Issue(s)
Fixes #36330
View session information ↗