Repository navigation
[PR] fix(release): train mode survives pre-#4449 patch lanes - #4576
Merged
Merged
Conversation
…anifest-sync script call and the manifest git-add (both fatal on lanes cut from tags older than b87732e)
ranxianglei
changed the title
Contributor
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.5522-pr.4576.8b4f8d4This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4576.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.822-master.d95799d # this exact build
npm install -g billion-context@master # always the newest merged build
|
This was referenced Oct 24, 2026
Merged
ranxianglei
added a commit
that referenced
this pull request
Oct 25, 2026
…ship PRs A patch lane cut from an old tag whose fixes already landed on master conflicts with master at ship time: the merge button refuses, resolving on the lane would leak unreleased master work into the published head tree, and resolving on master needs a direct master push. Also, lanes cut from old tags carry an old release-bugfix.yml that predates the bugfix-v* marker, so even a clean merge would silently skip publish. - add pull_request_target [labeled] trigger: the carve-out-ship label on an OPEN same-repo ship PR (bugfix-v* / bugfix-release/* head) publishes the PR head tree with every existing guard + full gate, no merge needed - run the master copy of the workflow (pull_request_target), fixing the old-tag lane marker gap for this path - manifest sync check fails open with a notice on pre-#4449 trees (same existence-guard philosophy as release-manual's lane guard, #4576) - annotate the ship PR after publish (audit trail; publish != merge) - document the label path in reference/release.md (carve-out + ship-the-lane)
Closed
ranxianglei
pushed a commit
that referenced
this pull request
Oct 26, 2026
…lane, missing-manifest gate, autoFold docs Three unfixed items from the #4725 review ledger (#4757 landed separately via the ci-fixes sweep): - release-bugfix.yml lost the #4449 manifest --check when the v3 lane rewrite landed (v0.1.208 ran it before Publish guard; master's rewrite dropped it). Ported back with the #4576 pre-#4449 lane existence guard, gated on the resolve step's actual proceed output (this variant has no path output). - scripts/sync-codex-plugin-version.mjs silently SKIPPED a missing manifest file — in --check mode a missing file greened the gate, neutering the release guard. A missing target is now a hard error naming the file; the four manifests are a fixed contract. Regression test added (RED on the old skip). - CONFIGURATION.md en+zh: document the autoFold benefit gate (#3444: growth folds arm only on ≥4096 tokens over the effective target; sub-4096 saving arms the backoff; image-dominant exempt) and the measured floor (irreducible baseline raises an unreachable target, never above the window). Both languages in sync. Sync tests 5/5, typecheck clean.
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.
Problem
Release (one-click)withtrain=truefails on any patch lane cut from a tag older than b87732e (bugfix-v<latest-tag>where the tree predates #4449):node scripts/sync-codex-plugin-version.mjsunconditionally —MODULE_NOT_FOUNDon lanes that don't carry the script yet. Nothing is published (safe abort), but the click flow is dead on exactly the lanes that need it.git add package.json package-lock.json .agents .claude-plugin plugins/codex—git addfatals on absent pathspecs (.agents,plugins/codexdon't exist in pre-[PR] feat: Codex Desktop Plugin (Git marketplace + MCP tools + version sync) | feat: Codex 桌面版插件（Git marketplace + MCP 工具 + 版本同步） #4449 trees).Hit while preparing the
bugfix-v0.1.206storage lane (5 storage fixes, #4390/#4444/#4506 follow-ups) — the lane is pushed and ready; this PR unblocks shipping it via one-click.Fix
::notice::when the script is absent (pre-[PR] feat: Codex Desktop Plugin (Git marketplace + MCP tools + version sync) | feat: Codex 桌面版插件（Git marketplace + MCP 工具 + 版本同步） #4449 lane — no manifests to sync anyway).git addlist with a per-path existence loop; theCHANGED/BADallowlist check is unchanged and still fails closed on unexpected files.Post-#4449 lanes are unaffected: script present → synced exactly as before.
Verification
yaml.safe_loadon the modified workflow passes.tsc --noEmitclean (the 5 carried fixes; this PR only touches the workflow file).