Skip to content

fix(release-notes): trim 0.1.192/0.1.191 summaries under the 400-char cap - #2818

Merged
ranxianglei merged 1 commit into
masterfrom
fix/release-notes-summary-cap
Oct 11, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
fix/release-notes-summary-cap

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Why

Publish Release Notes has been red since 2026-10-10 — the validator in release-notes.yml caps each entry's summary at 400 chars and exits on the first offender:

  • run 38040163381 (2026-10-10): 0.1.191 : summary too long (401 chars, cap 400)
  • run 38152721758 (2026-10-11): 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-notes is 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 main billion-context npm publish is unaffected (separate workflow; 0.1.193 published fine).

What

One file, two lines in release-notes/package.json:

entry before after change
0.1.192 520 399 condensed bilingual pair, all issue refs kept (#2658 #2596 #2664)
0.1.191 401 392 dropped the "ordinary " qualifier on fold drift

Verification

  • Ran the exact validation script from release-notes.yml locally against the edited payload: schema:1 ✓, 14 entries ✓, semver ✓, no dup ✓, tier ✓, every summary ≤400 ✓, dates ✓.
  • Round-trip JSON rewrite verified byte-identical formatting (only the two summary lines diff).

Follow-up (not in this PR)

A PR-lane guard (same validation extracted to scripts/release-notes-guard.mjs, called from ci.yml next to config-surface-guard) would catch over-cap entries before merge instead of after the master push. Happy to add on request.

… 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
@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: fix/release-notes-summary-cap (6b16f16)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.3121-pr.2818.7fed24d

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-pr2818.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei
ranxianglei merged commit 4b45e5c into master Oct 11, 2026
14 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.290-master.4b45e5c (rolling master tag).

npm install -g billion-context@0.0.290-master.4b45e5c  # this exact build
npm install -g billion-context@master  # always the newest merged build

npm view billion-context@master prints the current version at any time.

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