Skip to content

release v0.1.93 - #630

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-07_release-v0.1.93
Sep 7, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-09-07_release-v0.1.93

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

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

  1. ✅ This PR — merge → CI publishes 0.1.93
  2. Observe a real auto-upgrade: running install logs auto-updated 0.1.92 → 0.1.93
  3. Only then merge PR#204 (updateTag channel), which rides the NEXT release

Pre-flight

  • typecheck ✓
  • tests 1233/1235 (2 known plugin-agent.test.ts env fails) ✓
  • build ✓

@github-actions

github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-09-07_release-v0.1.93 (3163c93)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-630

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

Option B — Download artifact

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

This comment is automatically updated on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[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)

  • Head 2026-09-07_release-v0.1.93 @ 3163c93, base master, exactly one commit ahead: release v0.1.93 — message matches the CI trigger convention.
  • Diff vs master is only package.json: "version": "0.1.92" → "0.1.93". No lockfile drift, no content bundled into the release commit.

No-op premise holds

CI (head commit) — all 6 green: test × 4 (ubuntu/windows × node 22/24), version-guard, build-artifact. PR state: mergeable: true, mergeable_state: clean.

Local pre-flight on the branch

  • typecheck ✓ · build ✓ · tests 1234/1235 — one env-dependent failure, not a regression: tests/launcher.test.ts:1064 (resolveClientCommand: codex/claude resolve to themselves) asserts /usr/bin holds no codex; this sandbox has codex installed at /usr/bin/codex, so the resolver correctly returns the absolute path and the assertion fails. CI runners don't have it, which is why they're green. (The 2 plugin-agent.test.ts env fails noted in the OP didn't reproduce here — the env-fail set varies per machine; same class either way.)

Nothing left to do from my side. Sequence continues with you: merge #630 → CI publishes 0.1.93 → confirm a running install logs auto-updated 0.1.92 → 0.1.93 → then merge PR#204 on the next release. Per AGENTS.md I can't merge PRs myself.

@ranxianglei
ranxianglei merged commit 24d6b33 into master Sep 7, 2026
6 checks passed
@ranxianglei
ranxianglei deleted the 2026-09-07_release-v0.1.93 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