Advance workspace dependency bounds - #336
Draft
scotttrinh wants to merge 1 commit into
Draft
Conversation
Update existing exclusive upper bounds during release preparation when a planned sibling version reaches them. Leave unbounded dependencies alone and reject ambiguous constraints instead of guessing.
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
1 participant
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 a workspace package release reaches a dependent's existing exclusive upper bound, release preparation now advances that bound to the next compatibility boundary in the same generated release PR. This keeps deliberate compatibility bounds such as
vercel-internal-core<0.2.0from producing an uninstallable release when internal core first moves to0.2.0.