Repository navigation
chore(release): cut the hosted-cc and npm cohorts so workers get the op-log and mark fixes - #2237
Merged
Merged
Conversation
… protocol@0.86.1, recipe-runner@0.46.19, agent-runtime@0.48.2, recipe-cli@0.35.13 Cut both release groups so the operation-log and checklist-mark fixes reach workers. The published recipe-cli 0.35.12 went to npm at 07:34Z on 15 November and #2228 merged at 18:10Z the same day, so the tee that fills an operation log has never been published; harness 0.96.24 pins 0.35.11. The same gap holds for the mark work: published agent-runtime 0.48.1 predates #2232, and the harness pins 0.48.0. GLM 759e0f5a still showed 20 of 23 operation logs empty for exactly that reason. The hosted-cc group goes first because protocol has unreleased bullets, which the release tool refuses to leave behind an npm cut. Those hosted bullets are other lanes' work and go out as written. Dropped one bullet rather than publishing it: recipe-runner's unreleased consumer note for the mm-harness 0.96.23 cut told readers to keep recipe-runner 0.46.17 and protocol 0.85.0 unchanged, which is no longer true and would have misdirected the harness bump this cut exists to enable. Package | New version --- | --- @farmslot/command-center-ui | 0.36.5 @farmslot/command-center | 0.20.4 @farmslot/gateway | 0.39.5 @farmslot/protocol | 0.86.1 @farmslot/recipe-runner | 0.46.19 @farmslot/agent-runtime | 0.48.2 @farmslot/recipe-cli | 0.35.13
A published package resolves its workspace dependencies to exact versions, so the eight packages that depend on protocol, recipe-runner, agent-runtime or recipe-cli still pin the previous cohort until they are republished. Leaving them there makes mm-harness install two copies of the engine: adapter-sdk 0.27.9 pins protocol 0.86.0 and runner 0.46.18, adapter-rn 0.31.20 pins runtime 0.48.1. Every exact pinner of the four is in, not only the two found by hand: adapter-node, adapter-rn, adapter-sdk, adapter-web, capabilities, handoff, review-dispatch and skills all depend on at least one of them. The runner carries harness's consumer note for its 0.96.25 cut. The note went into 0.46.19 beside the cap it describes rather than into a release of its own: a second runner version whose only content is a note would have left the cohort with two runner versions and made the alignment bullets wrong. Package | New version --- | --- @farmslot/adapter-node | 0.8.20 @farmslot/adapter-rn | 0.31.21 @farmslot/adapter-sdk | 0.27.10 @farmslot/adapter-web | 0.19.17 @farmslot/capabilities | 0.7.4 @farmslot/handoff | 0.4.6 @farmslot/review-dispatch | 0.25.6 @farmslot/skills | 0.13.10
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
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 operation-log fix (#2228) has never been published.
@farmslot/recipe-cli0.35.12 went to npm at 07:34Z on 15 November; #2228 merged at 18:10Z the same day. Harness 0.96.24 pins 0.35.11, so a worker is two releases behind the fix — which is why GLM 759e0f5a still showed 20 of 23 operation logs empty. The same gap holds for the checklist-mark work: publishedagent-runtime0.48.1 predates #2232 (18:48Z) and the harness pins 0.48.0.What
Both groups, cut with
yarn release:cut. hosted-cc goes first because the release tool refuses to leave unreleased protocol bullets behind an npm cut; those hosted bullets are other lanes' work and go out as written.@farmslot/command-center-ui@farmslot/command-center@farmslot/gateway@farmslot/protocol@farmslot/recipe-runner@farmslot/agent-runtime@farmslot/recipe-clifarmslot_markschema@farmslot/adapter-node@farmslot/adapter-rn@farmslot/adapter-sdk@farmslot/adapter-web@farmslot/capabilities@farmslot/handoff@farmslot/review-dispatch@farmslot/skillsA published package resolves its workspace dependencies to exact versions, so every package depending on the four engine packages still pins the previous cohort until it is republished — which would make mm-harness install two copies of the engine. All eight exact pinners are in, not only the two found by hand:
adapter-node,adapter-rn,adapter-sdk,adapter-web,capabilities,handoff,review-dispatchandskillseach depend on at least one of the four.Two editorial calls, both stated so they can be reversed:
Follow-on, for the harness lane
metamask-harnessbumps@farmslot/protocol→ 0.86.1,@farmslot/recipe-runner→ 0.46.19,@farmslot/agent-runtime→ 0.48.2,@farmslot/recipe-cli→ 0.35.13,@farmslot/adapter-node→ 0.8.20,@farmslot/adapter-rn→ 0.31.21,@farmslot/adapter-sdk→ 0.27.10,@farmslot/adapter-web→ 0.19.17,@farmslot/handoff→ 0.4.6, then releases 0.96.25, then the skill path pin follows.yarn quality:changelogspasses. No implementation changes here.