Skip to content

release v0.1.100 - #676

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-10_release-v0.1.100
Sep 10, 2026
Merged

release v0.1.100#676
ranxianglei merged 1 commit into
masterfrom
2026-09-10_release-v0.1.100

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Release commit bumps 0.1.99 → 0.1.100 (package.json + package-lock.json only).

Ships since v0.1.99:

Merge → CI publishes 0.1.100.

@github-actions

Copy link
Copy Markdown

📦 Built Package Artifact

Branch: 2026-09-10_release-v0.1.100 (52e2685)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-676

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

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr676.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] 🏷 Release PR verified — ready for human merge.

Diff cleanliness (first gate)

  • Exactly one commit vs master: 52e2685 release v0.1.100 on branch 2026-09-10_release-v0.1.100.
  • Diff is version fields only: package.json (+1/-1) and package-lock.json (+2/-2), both 0.1.99 → 0.1.100. Nothing else touched — no content bundled into the release commit, per the one-version-one-commit rule.
  • Base is current master @ 175beb2 (includes fix #648: add hostUsageCredit switch to opt out of #408 host-usage backfill #649 hostUsageCredit, the only change since v0.1.99). GitHub reports mergeable, no conflicts.
  • npm registry check: latest published is 0.1.99, so 0.1.100 is free — no collision.

Pre-flight on head commit 52e2685 (same checks CI runs) ✅

  • npm ci: clean install (65 packages)
  • npm run typecheck: clean
  • npm test: 1270 pass / 0 fail (matches the 1270-test count in the PR body)
  • npm run build: success (self-contained dist/index.js)

No problems found while reviewing — nothing to fix or file.

Per system rules I can't merge PRs — please merge yourself: #676 . On merge, CI (release.yml) will publish 0.1.100 to npm, tag v0.1.100, and create the GitHub Release. Verify afterwards with npm view billion-context version.

中文摘要:v0.1.100 发布 PR 已核验——仅含版本号变更(package.json + lock,共 3 行)、基于最新 master、typecheck/1270 测试/build 全绿,无问题,可以合并。

@ranxianglei
ranxianglei merged commit 99bd512 into master Sep 10, 2026
6 checks passed
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