fix: release devtools as minor, not patch - #1160
Open
abhithesys wants to merge 1 commit into
Open
Conversation
abhithesys
added this pull request to stack #1161
September 11, 2026 05:49
An error occurred while trying to automatically change base from
abhishek/fix-release-ci
to
main
September 11, 2026 05:50
An error occurred while trying to automatically change base from
abhishek/fix-release-ci
to
main
September 11, 2026 05:50
react-lang 0.2.x depends on devtools ^0.1.0, so a devtools 0.1.x release carrying the new peer requirement (react-lang >=0.3.0) would be pulled into existing react-lang 0.2.x installs and break them with an unsatisfiable peer at install time. Releasing 0.2.0 instead escapes ^0.1.0: old react-lang keeps resolving old devtools, and only react-lang >=0.3.0 (released in the same train, depending on devtools ^0.2.0) picks up the new line. Same reasoning as react-email's minor in the original release-automation PR. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
AbhinRustagi
force-pushed
the
abhishek/devtools-changeset-minor
branch
from
September 11, 2026 05:50
bf81e70 to
f433a0e
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
AbhinRustagi
approved these changes
Sep 11, 2026
stack merge was automatically disabled
September 11, 2026 06:03
Pull Request is not mergeable
stack merge was automatically disabled
September 11, 2026 07:12
Pull Request is not mergeable
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
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.
react-lang 0.2.x depends on devtools ^0.1.0, so a devtools 0.1.x release carrying the new peer requirement (react-lang >=0.3.0) would be pulled into existing react-lang 0.2.x installs and break them with an unsatisfiable peer at install time. Releasing 0.2.0 instead escapes ^0.1.0: old react-lang keeps resolving old devtools, and only react-lang >=0.3.0 (released in the same train, depending on devtools ^0.2.0) picks up the new line. Same reasoning as react-email's minor in the original release-automation PR.