chore(template): label refresh _version -> v2.1.172 (clears sdk-drift)#498
Merged
Conversation
Contributor
Compat test: ✅ PASSEDRan Output |
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.
Auto label-sync — wire shape unchanged
Generated by
cc-drift-template-watch.ymlon 2026-06-11T06:39:16+00:00.capture-and-bake.mjs --checkcaptured live CC v2.1.172 andcomputeDriftreturned zero shape drift vs the bundled template — but the bundle's_versionlabel still read the previous version, whichcheck-sdk-drift.mjsflags against npm (thesdk-driftsignal). There is no wire-shape change to re-bake, so this PR bumps only the version-label fields:_versionand_supportedMaxTested->2.1.172claude-cli/<version>token in theuser-agentheader ->2.1.172_captured(last real capture) andx-stainless-package-versionare intentionally left untouched. Patch-bumped tov4.8.61so merging ships viacc-drift-auto-release.yml, and the nextsdk-drift-watchrun auto-closes the signal.Why auto-merge is safe here
Unlike a shape rebake (which a human reviews because the wire contract changed), this PR's empty
computeDriftis a proof that the tools / system_prompt / beta headers / field orders are byte-identical at v2.1.172. Only the label moves — the same deterministic-bump risk classcc-drift-watch.ymlalready auto-merges formaxTested. Auto-merge still gates on required checks (build x3, compat, test, docker-cap-drop-smoke); a red check leaves this PR open with the bot branch preserved.