fix(connector-jcode): version the package with its fixed group - #770
Merged
Conversation
PR #764 merged with connector-jcode at 0.25.0 while release #753 stamped the fixed changeset group at 0.26.0; the merged tree carries a version-skewed seed payload neither parent CI saw. The seed reconcile fails loud on it (by design), so every suite that boots the CLI is red on main: all four smoke shards and live fail with "installed at version 0.25.0 but the seed generation is 0.26.0". Bump the one package to the group version. No behavior change: the prepack skew assertion and the reconcile check are exactly the guards that caught this, and both pass at 0.26.0. Proof: pnpm smoke:adoption-doctor-e2e fails 7/10 on main ed0826d (CI, all shards) and passes 10/10 on this tree; typecheck 0; changeset status 0 (no changeset: version alignment of an unpublished tree, not a release).
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
1 participant
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.
Main
ed0826dcis red: #764 merged withconnector-jcodeat 0.25.0 while release #753 stamped the fixed changeset group at 0.26.0. Both parents were honestly green — the skew exists only in the merged tree. The seed reconcile fails loud on a version-skewed payload (by design), so every suite that boots the CLI fails on main: all four smoke shards andlive, withconnector "jcode" (@cotal-ai/connector-jcode) installed at version 0.25.0 but the seed generation is 0.26.0.Change: one line — bump
extensions/connector-jcode/package.jsonto the group version 0.26.0. The lockfile references the package by workspace link, so nothing else moves.Proof it fails without / passes with:
ed0826dc(runs 32512956967 and siblings) —smoke:adoption-doctor-e2e7/10 with the exact skew string above.pnpm buildrc=0,pnpm smoke:adoption-doctor-e2erc=0 (10/10),pnpm typecheckrc=0,pnpm changeset statusrc=0.No changeset: this aligns an unpublished tree with its own release stamp; the alternative cure is landing #766 (whose lockstep bump moves jcode to 0.27.0 and supersedes this line), but #766 currently carries its own unrelated shard-1 red (
smoke:delivery-renewal, evictPrincipal cell). This PR unbreaks main independently of that.Note for #759/#762/#763: their CI reds are inherited from this skew (identical failure string in their logs), not branch defects — they should re-run green once main is cured.