Repository navigation
chore(deps): update nx to 23.2.0 - #8
Merged
Merged
Conversation
FrozenPandaz
approved these changes
Sep 2, 2026
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
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
nx and @nx/* on 23.1.1.
Expected Behavior
nx and @nx/* on 23.2.0-beta.11, staged for the 23.2.0 stable release. Minor bump - migrations ran clean and made no code changes; package.json + lockfile only.
Verified locally on this branch: workspace has no projects, so run-many is a no-op; graph loads warning-free.
npm cireports the lockfile in sync.nx format:checkclean.Draft until 23.2.0 stable is published - a follow-up commit will move the pin from the beta to the release.
Related Issue(s)
NXC-4911