Repository navigation
[PR] chore: sync master version to 0.1.208 (unblock one-click release drift guard, run 40520077248) - #4980
Merged
Conversation
The 0.1.208 carve-out lane shipped off the v0.1.207 tag (storage v8 emergency, #4677) without landing a version bump on master, so master's package.json (0.1.207) no longer equals npm latest (0.1.208) and the one-click release drift guard aborts (run 40520077248, step 'Drift guard'). Version-string sync ONLY: master already carries the 0.1.208 content under its own commits (#4708 for #4677, #4666). Plugin manifests synced via scripts/sync-codex-plugin-version.mjs (#4449) so the publish workflows' --check gate stays green. No code change; branch deliberately does NOT match *_release-v* so merging publishes nothing.
ranxianglei
force-pushed
the
2026-10-27_sync-version-0.1.208
branch
from
October 27, 2026 14:51
a4707b8 to
6e60ec1
Compare
Contributor
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.6502-pr.4980.9f05f39This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4980.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.886-master.bcbd1a3 # this exact build
npm install -g billion-context@master # always the newest merged build
|
This was referenced Oct 27, 2026
Merged
ranxianglei
pushed a commit
that referenced
this pull request
Oct 27, 2026
…t — merge-guard sync Master advanced 7f2e119 -> 9b6ec23 (+5 commits: version 0.1.208 #4980; dsh direct-fallback oversize guard #4904/#4894 in dsh-native.ts/native-intercept.ts + tests). Clean auto-merge, zero conflicts (delta touches no PR-area or prior-conflict file). PR change intact: src/server.ts zero-fold calibrated-fit predicate (#4930) + tests/issue4930-zero-fold-calibrated-fit.test.ts. Typecheck clean; targeted PR/preflight/yield suites 48/48 green.
This was referenced Oct 27, 2026
Merged
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.
What
Sync master's version string 0.1.207 → 0.1.208, plus the four plugin manifests (
scripts/sync-codex-plugin-version.mjs, #4449) andpackage-lock.json. Six files, version strings only, no code change.Why
The 0.1.208 carve-out shipped off the v0.1.207 tag (storage v8 emergency, #4677) and never landed a version bump on master. Result: master
package.json(0.1.207) != npm latest (0.1.208) and the one-click release (release-manual.yml) aborts at its Drift guard — run 40520077248, failed stepDrift guard, errormaster package.json (0.1.207) != npm latest (0.1.208). Every future master release is blocked until the string catches up.Content-wise master is NOT behind 0.1.208: the storage fixes landed via #4708 (#4677) and #4666. This is purely the version-string wedge the carve-out channel leaves behind (reference/release.md: master is re-aligned after every publish — the lane's auto alignment PR did not appear for this ship).
Scope / safety
*_release-v*/bugfix-release/*so merging publishes nothing and triggers no release workflow.package.jsonfor the publish workflows'--checkgate ([PR] feat: Codex Desktop Plugin (Git marketplace + MCP tools + version sync) | feat: Codex 桌面版插件(Git marketplace + MCP 工具 + 版本同步) #4449) — synced and verified (--checkgreen).2026-10-26_release-v0.1.209branch bumps the same lines and will need a trivial rebase (207→209 vs 208→209).Config surface
None.