Repository navigation
chore: sync master version metadata to v0.1.192 (Release drift guard) - #2765
Merged
Merged
Conversation
v0.1.192 was a carve-out release (78df4ea, #2664 only) and its version bump never flowed back to master, so master still declares 0.1.191 while npm latest is 0.1.192. That trips the Release one-click Drift guard: ::error::master package.json (0.1.191) != npm latest (0.1.192) #2664's changes themselves are already in master (f0b3f5d), so this is metadata-only: bump package.json + package-lock.json (root and packages."" entries) to 0.1.192 so the next one-click release (0.1.193, carrying the #2755 fold-summary head-stability fix) can proceed.
Contributor
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.3038-pr.2765.1b1b950This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2765.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Contributor
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.276-master.9dd4a36 # this exact build
npm install -g billion-context@master # always the newest merged build
|
Owner
Author
[bot] 🏷 已核实:此同步已完成并合入 master,无需再动。 Drift guard 现在会通过,可以直接 re-dispatch。 核实证据(全部实测):
结构化八问:
收工判定:完成,可收工。owner 可以重新 dispatch Release (one-click) target |
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 one-click Release workflow run 38133050838 (target 0.1.193) failed at the Drift guard:
v0.1.192 was a carve-out release (
78df4eaa, #2664 only, on top of v0.1.191) and its version bump never flowed back to master — unlike v0.1.191, which was synced via #2630.What
Metadata-only bump
0.1.191 → 0.1.192:package.jsonpackage-lock.json(rootversion+packages."".version)#2664's code changes are already in master via
f0b3f5d6, so master is content-wise a superset of v0.1.192; nothing but the version fields was stale. Precedent: aeac5a8.After merge
Re-dispatch Release (one-click) with target
0.1.193— that release will carry the #2755 fold-summary head-stability fix (kernel 0.0.116).kernel-change: none