Skip to content

Revert "feat: force-update out of critical-defect versions via remote advisories" (#1483) — re-land after no-op v0.1.166 - #1580

Merged
ranxianglei merged 1 commit into
masterfrom
revert-1483-until-noop
Sep 28, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
revert-1483-until-noop

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Why

Discipline order (AGENTS.md §5, auto-update mechanism rule): a change to src/update.ts must 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

  1. Merge this revert → master is clean of advisory code.
  2. Merge release v0.1.166 #1578 → CI publishes v0.1.166 (version bump only).
  3. Observe a real running install auto-update 0.1.165 → 0.1.166 on the OLD updater code (log line ✔ billion-context auto-updated 0.1.165 → 0.1.166).
  4. Re-land feat: force-update out of critical-defect versions via remote advisories #1483 (branch 2026-09-27_advisory-force-update unchanged, still clean vs post-revert master) → ships in v0.1.167.
  5. Then the empty-advisory dry run (companion package → CI publish → watcher → banner → recovery).

If step 3 fails, STOP — investigate the existing path before re-landing.

…-force-update"

This reverts commit 6de711d, reversing
changes made to 1c60633.
@ranxianglei
ranxianglei merged commit febcc92 into master Sep 28, 2026
13 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: revert-1483-until-noop (44171bf)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.1512-pr.1580.dfdd48e

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

Option B — Download artifact

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

Install instructions are refreshed on each push.

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