Repository navigation
Preserve deprecated explicit pre-release mode - #20246
Merged
charliermarsh merged 3 commits intoJul 8, 2026
Merged
charliermarsh merged 3 commits into
charliermarsh merged 3 commits into
Conversation
charliermarsh
marked this pull request as ready for review
July 8, 2026 15:28
charliermarsh
merged commit Jul 8, 2026
4c394d2
into
charlie/transitive-prerelease-pubgrub
55 of 56 checks passed
charliermarsh
added a commit
that referenced
this pull request
Jul 10, 2026
## Summary The parent PR currently treats `explicit` as an alias for `if-necessary-or-explicit`, which changes existing configurations to fall back to pre-releases when no stable candidate satisfies the active constraints. This restores the standalone `explicit` policy with its legacy solve-static behavior: only first-party requirements with explicit pre-release specifiers authorize pre-releases, packages without that authorization do not fall back, and transitive pre-release requirements do not enable the mode dynamically. Keeping the authorization set fixed before resolution preserves PubGrub's candidate-universe assumptions, including the legacy scoped-override behavior. (The mode remains deprecated, but we warn rather than failing.)
charliermarsh
added a commit
that referenced
this pull request
Jul 14, 2026
## Summary The parent PR currently treats `explicit` as an alias for `if-necessary-or-explicit`, which changes existing configurations to fall back to pre-releases when no stable candidate satisfies the active constraints. This restores the standalone `explicit` policy with its legacy solve-static behavior: only first-party requirements with explicit pre-release specifiers authorize pre-releases, packages without that authorization do not fall back, and transitive pre-release requirements do not enable the mode dynamically. Keeping the authorization set fixed before resolution preserves PubGrub's candidate-universe assumptions, including the legacy scoped-override behavior. (The mode remains deprecated, but we warn rather than failing.)
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.
Summary
The parent PR currently treats
explicitas an alias forif-necessary-or-explicit, which changes existing configurations to fall back to pre-releases when no stable candidate satisfies the active constraints.This restores the standalone
explicitpolicy with its legacy solve-static behavior: only first-party requirements with explicit pre-release specifiers authorize pre-releases, packages without that authorization do not fall back, and transitive pre-release requirements do not enable the mode dynamically. Keeping the authorization set fixed before resolution preserves PubGrub's candidate-universe assumptions, including the legacy scoped-override behavior.(The mode remains deprecated, but we warn rather than failing.)