Repository navigation
Revert "feat: force-update out of critical-defect versions via remote advisories" (#1483) — re-land after no-op v0.1.166 - #1580
Merged
Conversation
Contributor
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.1512-pr.1580.dfdd48eThis exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr1580.tgz
npm install -g packageInstall instructions are refreshed on each push. |
This was referenced Sep 28, 2026
Merged
Merged
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.
Why
Discipline order (AGENTS.md §5, auto-update mechanism rule): a change to
src/update.tsmust ship after a no-op release proves the currently-running fleet's upgrade path — not before. #1483 was merged ahead of its no-op validation release (#1578, still open), so the published v0.1.166 would have carried the new updater code and the validation would no longer be pure.This PR
Pure revert of the #1483 merge (
git revert -m 1 6de711d, 19 files, −1074/+6). Nothing else.Sequence from here
✔ billion-context auto-updated 0.1.165 → 0.1.166).2026-09-27_advisory-force-updateunchanged, still clean vs post-revert master) → ships in v0.1.167.If step 3 fails, STOP — investigate the existing path before re-landing.