Repository navigation
release v0.1.75 - #484
Merged
Merged
release v0.1.75#484
Conversation
Contributor
📦 Built Package ArtifactBranch: Option A — Install from npm PR tag (recommended)npm install -g billion-context@pr-484Each push to this PR publishes a new version under the Option B — Download artifact
tar xzf billion-context-pr484.tgz
npm install -g packageThis comment is automatically updated on each push. |
Owner
Author
[bot] 🏷 Verified independently on Commit hygiene
Pre-flight (re-run by me, clean
Verdict: release commit is clean and isolated, pre-flight green modulo a pre-existing env-dependent test. Ready for human merge — CI will publish on merge as usual. I won't merge (human-only). |
This was referenced Sep 30, 2026
Closed
ranxianglei
pushed a commit
that referenced
this pull request
Oct 3, 2026
…eady path (#1960) The steady request path (client echoes the round back) silently dropped redacted_thinking blocks because anthropicToCore had no case for them, so every later request rebuilt the latest assistant message without the block and Anthropic answered 400 "cannot be modified" forever — the half of #1960 that kept the session stuck after the compress turn. - acp-kernel pin 0.0.99 → 0.0.101 (exact), which carries kernel PR #500 (redacted_thinking sidecar round-trip). Also rides along from v0.0.100+: #483 ref capacity widened to 9,999,999, #484 case-insensitive protected tool matching, #478 nudge cadence re-anchor, #493 language-preservation behind an opt-in flag (default off), and #499 prune/recommend shared per-turn index (hundreds of ms saved on ordinary requests in large sessions — release-note material). - tests/issue1960-steady-redacted.test.ts: client-echoed [thinking(sig), redacted(data), tool_use] must survive prepare→outbound byte-identical in order. Verified failing on 0.0.99, passing on 0.0.101. Preflight: typecheck clean; targeted loop/thinking/reasoning suites 186/186 green incl. both new #1960 files; build OK.
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.
Version bump only (
0.1.74→0.1.75) +package-lock.jsonversion fields synced (they had drifted to0.1.71across the last few releases;npm install --package-lock-onlytouched nothing else).Changes since v0.1.74
markCompactionBoundary+POST /__bili/plugin/compact+applyCompactionArchivemax_tokensclamp (clampOutputBudget/estimateInputTokens) + emergency nudge at 0.7Full diff: 7 non-merge commits since
v0.1.74.Pre-flight (local, on this branch)
npm run typecheck✓npm test— 966/968 (2 = known permanentplugin-agent.test.tsenv failures, reproduce on clean master)npm run build✓Merge is human-only as always; CI publishes on merge.