Repository navigation
chore: sync master package version to npm latest 0.1.182 (bugfix-channel back-sync) - #2054
Merged
Merged
Conversation
Contributor
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.2097-pr.2054.d774aebThis exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2054.tgz
npm install -g packageInstall instructions are refreshed on each push. |
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
One-click release run 37187707188 failed at the drift guard:
0.1.182 was published from the new bugfix-release channel (
bugfix-release/v0.1.182-integer-max-tokens, #2011 integer max_tokens hotfix). That channel publishes from a side branch and has no back-sync step, so the version bump never landed on master. The code fix itself is already on master (PR #2012); the release-notes entry for 0.1.182 was also already present — only thepackage.json/package-lock.jsonversion bump was missing.What
Cherry-pick of the single missing commit from the bugfix branch:
5a9d84aerelease v0.1.182 (package.json + package-lock.json 0.1.181 → 0.1.182)After merging this, re-run the one-click release: it will pass the drift guard and release 0.1.183 with everything since.
Follow-up (separate)
The bugfix-release channel should open an automatic back-sync PR to master after publishing, so this drift class cannot recur (release-bugfix.yml currently leaves master behind after every hotfix).
Drift guard behaved correctly — this is exactly the situation it exists to catch.