fix(release): rename stale @objectstack/create-objectstack refs in pending changesets - #3635
Merged
Merged
Conversation
…nding changesets changeset version hard-fails on a changeset naming a package that is not in the workspace, and two pending changesets (better-auth-1-7-0-rc-2 batch, OSV 2026-07 batch) still said @objectstack/create-objectstack while the scaffolder package is named create-objectstack. With the hotcrm gate now advisory in pre-mode (#3627), this was the next and only blocker in the version step: the v17 train died before creating its Version Packages PR. Verified locally: changeset status reproduced the exact CI error before the rename and assembles the release plan cleanly after it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ECTCrcCdZpCHw5zFSgcmGt
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
github-actions
Bot
added
size/xs
documentation
os-zhuang
marked this pull request as ready for review
July 27, 2026 11:49
os-zhuang
added a commit
that referenced
this pull request
Jul 31, 2026
…hangeset (#4302) changeset version hard-fails on a changeset naming a package that is not in the workspace, and adapter-hono-auth-wildcard-yields still said @objectstack/adapter-hono while the workspace package is named @objectstack/hono. Same class of blocker as #3635: it kills the version step of the v17 train before the Version Packages PR can be created. A sweep of all 559 pending changesets' frontmatter (974 package refs) and pre.json initialVersions against the 77 workspace package names found no other stale reference. Adds an empty changeset for the Check Changeset gate; releases nothing. Co-authored-by: Jack Zhuang <277994282+os-zhuang@users.noreply.github.com> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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.
Why — the v17 train's next (and only remaining) blocker
With the hotcrm gate now advisory in pre-mode (#3627), the Release run on main got past the smoke for the first time all day — and immediately hit the next failure, inside
pnpm run version:changeset versionhard-fails on any changeset that names a package not present in the workspace. Two pending changesets still reference the scaffolder by its old scoped name@objectstack/create-objectstack, while the workspace package (and itspre.jsoninitialVersions entry) is namedcreate-objectstack:.changeset/better-auth-1-7-0-rc-2-and-prod-dep-batch.md.changeset/osv-batch-2026-07-dep-bumps.mdA full sweep of every
.changeset/*.mdfrontmatter againstpnpm m ls(78 workspace packages) found exactly these two stale references — nothing else.What
Renamed the two entries to
"create-objectstack": patch(the bump intent is preserved — both batches touch scaffolder deps). Added an empty changeset to satisfy the Check Changeset gate; it releases nothing.Verification
pnpm exec changeset statusreproduced the exact CI error before the rename, and assembles the release plan cleanly after it.pnpm run version(changeset version+ protocol/template sync scripts) completes cleanly and computes17.0.0-rc.0across the fixed group, including the blank-template lockstep sync (8@objectstack/*ranges →^17.0.0,engines.protocol→^17). Version artifacts were discarded after verification; only the changeset renames ship.After merge, the next Release run on main should finally create the
chore: version packagesPR for17.0.0-rc.0.🤖 Generated with Claude Code
https://claude.ai/code/session_01ECTCrcCdZpCHw5zFSgcmGt
Generated by Claude Code