Repository navigation
release v0.1.123 - #998
Merged
Merged
release v0.1.123#998
Conversation
Contributor
📦 Built Package ArtifactBranch: Option A — Install from npm PR tag (recommended)npm install -g billion-context@pr-998Each push to this PR publishes a new version under the Option B — Download artifact
tar xzf billion-context-pr998.tgz
npm install -g packageInstall instructions are refreshed on each push. |
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.
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:
bili plugin install dshshould go through the bundle channel + auto-update rewrite #966 (already shipped inside 0.1.122, without the no-op flow):src/update.tsgained therefreshDshProfileBundleshook 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.checkForUpdate/installViaTarballdecision 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
[update] installed 0.1.122 → 0.1.123. Restart to finish.Pre-flight
npm run typecheck✅npm test— 1950 pass / 0 fail / 2 skipped (E2E gate) ✅npm run build✅package.json(no lockfile drift) ✅