fix: peer-window mismatch that broke the release publish - #1186
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
0.17.0 while assistant-ui and react-ui still declared peer windows '>=0.14.0 <0.17.0' — excluding the version actually being published. The UI-pair minor crossed the upper bound and nobody moved the dependents' windows in that train. Widen the three affected windows to <0.17.0. Also run verify-peer-windows.mjs inside version:ci (right after changeset version), so a stale window now fails when the Version Packages PR is generated, surfacing on that run instead of at publish-after-merge.
abhithesys
force-pushed
the
abhishek/fix-peer-windows
branch
from
September 15, 2026 14:12
5a185e4 to
276478f
Compare
abhithesys
enabled auto-merge (squash)
September 15, 2026 14:14
vishxrad
approved these changes
Sep 15, 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
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.
fix: peer-window mismatch that broke the release publish
The last Release run failed at publish (run):
verify-peer-windows.mjsblocked it becausereact-ui/react-headlessshipped at 0.16.0 whileassistant-uiandreact-uistill declared peer windows>=0.14.0 <0.16.0— a range that excludes the 0.16.0 they ship against. The UI-pair minor crossed the window's upper bound and no PR moved the dependents' windows in that train.Changes
<0.17.0(react-ui → react-headless; assistant-ui → react-headless; assistant-ui → react-ui) so they include the 0.16.x line. The guard now passes.verify-peer-windows.mjsinsideversion:ci(right afterchangeset version), so a stale window fails when the Version Packages PR is generated — surfacing on that run instead of at publish-after-merge, as it did here.After merge
Re-run the failed Release workflow (or push to
main): with the windows fixed, the publish path succeeds and the already-bumped 0.16.0 versions get published + tagged.Follow-up (not in this PR)
This surfaces stale windows earlier but doesn't stop them recurring — the windows are still hand-maintained, so
<0.17.0just moves the next break to 0.17.0. The durable fix is async-peer-windows.mjsthat derives each window from the just-bumped versions afterchangeset version, eliminating the manual chase. Proposed separately.🤖 Generated with Claude Code