Skip to content

release v0.1.123 - #998

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-19_release-v0.1.123
Sep 19, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-09-19_release-v0.1.123

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

No-op validation release (pure version bump, zero code changes vs deployed 0.1.122).

Diff vs released v0.1.122 = this version bump only (master's only other change since the tag is README docs).

Why a no-op (AGENTS.md §5 auto-update rule)

Two stacked, not-yet-validated changes to the auto-update path are pending:

  1. [dsh] unify install lanes: bili plugin install dsh should go through the bundle channel + auto-update rewrite #966 (already shipped inside 0.1.122, without the no-op flow): src/update.ts gained the refreshDshProfileBundles hook on self-update — 6 lines that have never executed a real-world upgrade: the 0.1.121 → 0.1.122 hop this morning was performed by 0.1.121's code.
  2. fix: single-writer plugin guard — never overwrite host-managed copies (#991) #995 (single-writer plugin guard, still open): changes checkForUpdate/installViaTarball decision logic.

Per AGENTS.md §5, updater changes must be preceded by a no-op release proving the existing upgrade path. The next hop (0.1.122 → 0.1.123) will be executed by 0.1.122's updater — validating #966's hook and the plumbing — using code we already trust, independent of #995.

Validation plan

  1. Merge this PR → CI publishes 0.1.123.
  2. A local bili process running 0.1.122 (already in place) auto-updates; log must show [update] installed 0.1.122 → 0.1.123. Restart to finish.
  3. Only then merge fix: single-writer plugin guard — never overwrite host-managed copies (#991) #995 and release 0.1.124 normally.

Pre-flight

  • npm run typecheck ✅
  • npm test — 1950 pass / 0 fail / 2 skipped (E2E gate) ✅
  • npm run build ✅
  • Commit changes ONLY package.json (no lockfile drift) ✅

@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-09-19_release-v0.1.123 (39bf164)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-998

Each push to this PR publishes a new version under the pr-998 npm tag.

Option B — Download artifact

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

Install instructions are refreshed on each push.

@ranxianglei
ranxianglei merged commit cc53ca0 into master Sep 19, 2026
8 checks passed
@ranxianglei
ranxianglei deleted the 2026-09-19_release-v0.1.123 branch October 15, 2026 05:32
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