Skip to content

docs(release-notes): add v0.1.183 entry (#1870) - #2055

Closed
ranxianglei wants to merge 1 commit into
masterfrom
2026-10-04_release-notes-0.1.183
Closed

ranxianglei wants to merge 1 commit into
masterfrom
2026-10-04_release-notes-0.1.183

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

One-click release run 37188425653 passed the drift guard (after #2054) but stopped at the release-notes gate:

release 0.1.183 has no release-notes entry (tier + model-written summary).
Add it to release-notes/package.json and merge to master BEFORE dispatching (#1870).

Entry (recommended, 370ch) covers the 0.1.183 master wave since 0.1.181:

Merge this, then re-dispatch the one-click release.

@github-actions

github-actions Bot commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-04_release-notes-0.1.183 (ba88841)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.2098-pr.2055.22a051b

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Option B — Download artifact

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

Install instructions are refreshed on each push.

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