Repository navigation
release v0.1.93 - #630
release v0.1.93#630
Conversation
📦 Built Package ArtifactBranch: Option A — Install from npm PR tag (recommended)npm install -g billion-context@pr-630Each push to this PR publishes a new version under the Option B — Download artifact
tar xzf billion-context-pr630.tgz
npm install -g packageThis comment is automatically updated on each push. |
[bot] 🏷 Verified — PR #630 is correct and ready for human merge. This is a release-PR mirror (not a bug/feature), so triage = duplicate screen + validity audit: no duplicates (the PR itself already exists, open), and every claim in the body checks out against the repo: Branch / commit purity (§5 rule compliance)
No-op premise holds
CI (head commit) — all 6 green: test × 4 (ubuntu/windows × node 22/24), version-guard, build-artifact. PR state: Local pre-flight on the branch
Nothing left to do from my side. Sequence continues with you: merge #630 → CI publishes 0.1.93 → confirm a running install logs |
No-op validation release (version bump only) — first step of the AGENTS.md §5 sequence for PR#204.
Why
PR#204 changes
src/update.ts(version-check + update channel). Per AGENTS.md §5, any change to the auto-update mechanism itself must be validated with a no-op release FIRST: prove the existing upgrade path is healthy end-to-end before the new updater code ships.What's in 0.1.92 → 0.1.93
Code already on master since v0.1.92:
Neither touches
src/update.ts. This release commit itself is the version bump only.Sequence
auto-updated 0.1.92 → 0.1.93Pre-flight
plugin-agent.test.tsenv fails) ✓