Skip to content

chore: restore version lockstep across all seven packages - #52

Merged
pbWise merged 1 commit into
mainfrom
fix/restore-version-lockstep
Aug 2, 2026
Merged

chore: restore version lockstep across all seven packages#52
pbWise merged 1 commit into
mainfrom
fix/restore-version-lockstep

Conversation

@pbWise

@pbWise pbWise commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

Summary

  • 0.18.0 released core/compiler/cli alone — the two changesets behind it named only those three packages, leaving react/orpc/testing/webmcp at 0.17.1.
  • Same failure/cause as the 0.6.0, 0.11.0 and 0.14.0 breaks (documented in .changeset/README.md).
  • Hand-edits the four laggards' package.json up to 0.18.0 (matching the current line, published nowhere) and adds one grouped changeset naming all seven packages so the next release carries them together to 0.19.0.
  • npx changeset status --verbose confirms all seven resolve to 0.19.0.

Test plan

  • npx changeset status --verbose — all seven packages bump to 0.19.0 as minor
  • Merge this PR → CI opens/updates the "chore: version packages" PR
  • Merge that version PR to publish 0.19.0 for all seven packages to npm

0.18.0 shipped core/compiler/cli alone: their changesets named only the
packages whose code had changed, but the frontmatter is a lockstep
declaration, not a description of the diff (.changeset/README.md). Same
failure as 0.6.0, 0.11.0, 0.14.0.

Laggards hand-edited 0.17.1 -> 0.18.0; one grouped changeset carries all
seven to 0.19.0. The four have no 0.18.0 on npm - that gap is the repair.
No functional change.
@vercel

vercel Bot commented Aug 2, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
agent-surface-docs Ready Ready Preview Aug 2, 2026 2:07pm

Request Review

@pbWise
pbWise merged commit e3f7037 into main Aug 2, 2026
8 of 9 checks passed
@pbWise
pbWise deleted the fix/restore-version-lockstep branch August 2, 2026 14:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant