feat(release)!: useLegacyVersioning is false by default, migrate config#30838
Merged
FrozenPandaz merged 2 commits intomasterfrom Apr 25, 2025
Merged
feat(release)!: useLegacyVersioning is false by default, migrate config#30838FrozenPandaz merged 2 commits intomasterfrom
FrozenPandaz merged 2 commits intomasterfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
Contributor
|
View your CI Pipeline Execution ↗ for commit 629f8ac.
☁️ Nx Cloud last updated this comment at |
d9f48c1 to
6bf8d16
Compare
6bf8d16 to
4e7f56e
Compare
JamesHenry
commented
Apr 24, 2025
FrozenPandaz
approved these changes
Apr 25, 2025
Contributor
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR updates
nx releaseto use the revamped versioning implementation by default. It also updates and adds relevant documentation, and provides an automated migration for the new configuration structure.For anyone exclusively versioning TS/JS packages, there should be no real difference to your experience (although a number of bugs have been fixed and new features around updating multiple
package.jsonfiles at once are now available to you with this change).For the lifecycle of Nx v21,
release.version.useLegacyVersioningwill remain as a option that can be set totrueto revert to the old behavior and configuration structure.NOTE: This should only be a temporary solution, for example if one of the plugins you use does provide a
VersionActionsbased versioning implementation yet. The option and legacy implementation will be removed entirely in Nx v22 (in ~6 months).BREAKING CHANGE:
VersionActionsin Nx 20.8 when it was opt-in, there are breaking changes to the abstract class here as well.manifestRootsToUpdatehas gone fromstring[]tomanifestsToUpdate: { manifestPath: string; preserveLocalDependencyProtocols: boolean; }[]to support controlling the local dependency updates per manifest in order to support advanced source vs dist scenarios, and correspondinglyisLocalDependencyProtocolhas been removed from the abstract class and the method will no longer be called from the core logic. It should be thought of as an implementation detail ofupdateProjectDependenciesinstead.