Skip to content

[PR] chore: sync master version to 0.1.208 (unblock one-click release drift guard, run 40520077248) - #4980

Merged
ranxianglei merged 1 commit into
masterfrom
2026-10-27_sync-version-0.1.208
Oct 27, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-10-27_sync-version-0.1.208

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

What

Sync master's version string 0.1.207 → 0.1.208, plus the four plugin manifests (scripts/sync-codex-plugin-version.mjs, #4449) and package-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 step Drift guard, error master 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

Config surface

None.

@ranxianglei ranxianglei changed the title chore: sync master version to 0.1.208 (unblock one-click release drift guard, run 40520077248) [PR] chore: sync master version to 0.1.208 (unblock one-click release drift guard, run 40520077248) Oct 27, 2026
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
ranxianglei force-pushed the 2026-10-27_sync-version-0.1.208 branch from a4707b8 to 6e60ec1 Compare October 27, 2026 14:51
@github-actions

github-actions Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-27_sync-version-0.1.208 (6e60ec1)

Latest build — install this exact version

npm install -g billion-context@0.0.6502-pr.4980.9f05f39

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Recent builds (commit → version)

commit version build
6e60ec1 billion-context@0.0.6502-pr.4980.9f05f39 build
a4707b8 billion-context@0.0.6501-pr.4980.9b5d249 build

Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr4980.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei
ranxianglei merged commit bcbd1a3 into master Oct 27, 2026
24 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.886-master.bcbd1a3 (rolling master tag).

npm install -g billion-context@0.0.886-master.bcbd1a3  # this exact build
npm install -g billion-context@master  # always the newest merged build

npm view billion-context@master prints the current version at any time.

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant