feat(release)!: release graph aware filtering, updateDependents can now be "always"#32971
Merged
JamesHenry merged 1 commit intomasterfrom Oct 8, 2025
Merged
feat(release)!: release graph aware filtering, updateDependents can now be "always"#32971JamesHenry merged 1 commit intomasterfrom
JamesHenry merged 1 commit intomasterfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
View your CI Pipeline Execution ↗ for commit dbcad4f
☁️ Nx Cloud last updated this comment at |
c13fda2 to
1120b4e
Compare
1120b4e to
6bf3909
Compare
6bf3909 to
e130797
Compare
e130797 to
4574b5d
Compare
4574b5d to
d967ef1
Compare
d967ef1 to
dbcad4f
Compare
4 tasks
Coly010
approved these changes
Oct 8, 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.
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.
When release groups changed to become more flexible and powerful, with
updateDependentstracing across any number of transitive release groups, the logic for filtering (e.g.--projectsand--groupson the CLI) was never updated to reflect this new dynamism and complexity.Now in this PR, release graph construction has been fully separated out from the release-group-processor. It now lives in the new
ReleaseGraph. This is also now where filtering takes place so that the filters can be fully graph aware.There is additionally a new
alwaysoption available forupdateDependentsin addition toautoandneverwhich are unchanged.alwaysmeans that a project's dependents will be updated wherever they may live in the graph, regardless of whether or not they were directly included within a project or graph filter. We feel that this is what people want most of the time so this is also going to become the default in a follow up breaking change PR. In order to be easier to review, and to increase confidence in this refactor, this PR does not yet make that change to leave as many tests as possible untouched (other than utilities changing).BREAKING CHANGE: The signature of
init()onVersionActionshas changed, it no longer accepts a second argument. Validation of the manifest files, if any, now takes place via a separate method (validate()) call after construction of the newReleaseGraph. For the most part, users do not need customVersionActionsso only a small percentage of consumers should be impacted.Fixes #31273