Repository navigation
fix(release-notes): trim 0.1.192/0.1.191 summaries under the 400-char cap - #2818
Merged
Merged
Conversation
… cap Publish Release Notes has been red since 2026-10-10: the 0.1.191 backfill entry landed at 401 chars, and the 0.1.192 backfill (f24e3e8) added a 520-char bilingual summary. The validator exits on the first offender, so both must be trimmed in the same push. - 0.1.192: 520 -> 399 (condense the bilingual pair, keep #2658/#2596/#2664 refs) - 0.1.191: 401 -> 392 (drop the 'ordinary ' qualifier on fold drift) Verified locally with the exact validation script from release-notes.yml (schema:1, 1..20 entries, semver, dedup, tier, <=400 summary, date) — all 14 entries pass. Fixes the failed runs: - https://github.com/ranxianglei/billion-context/actions/runs/38152721758 - https://github.com/ranxianglei/billion-context/actions/runs/38040163381
Contributor
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.3121-pr.2818.7fed24dThis exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2818.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Contributor
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.290-master.4b45e5c # this exact build
npm install -g billion-context@master # always the newest merged build
|
This was referenced Oct 11, 2026
Merged
Closed
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.
Why
Publish Release Noteshas been red since 2026-10-10 — the validator inrelease-notes.ymlcaps each entry'ssummaryat 400 chars and exits on the first offender:0.1.191 : summary too long (401 chars, cap 400)0.1.192 : summary too long (520 chars, cap 400)— 0.1.192 entry added by f24e3e8 (bilingual EN丨中文 backfill)Consequence: the companion package
billion-context-release-notesis stuck at 0.0.10 (2026-10-06) — the proxy's update-visibility watcher (#1870) never saw the critical 0.1.192 / 0.1.193 entries, so users get no upgrade banner. The mainbillion-contextnpm publish is unaffected (separate workflow; 0.1.193 published fine).What
One file, two lines in
release-notes/package.json:Verification
release-notes.ymllocally against the edited payload: schema:1 ✓, 14 entries ✓, semver ✓, no dup ✓, tier ✓, every summary ≤400 ✓, dates ✓.Follow-up (not in this PR)
A PR-lane guard (same validation extracted to
scripts/release-notes-guard.mjs, called fromci.ymlnext toconfig-surface-guard) would catch over-cap entries before merge instead of after the master push. Happy to add on request.