release: 0.32.1 - #192
Merged
Merged
Conversation
Ships the #186 fix (merged in #191): a source-disclaimer sentence no longer counts its bracketed ids as unsupported citations, so being transparent about discarded sources stops costing the answer its supportRatio. Patch, not minor — no API change. `VerificationReport` gains an additive `disclaimers` field; the only consumers (agent.ts, cli.ts) read `.unsupported`. Verified before opening: extract-release-notes.cjs resolves the new `## [0.32.1]` section (empty release notes was the #135 failure mode), package-lock version tracks package.json at 0.32.1, typecheck clean, 859 tests / 0 failures. Merging this fires auto-release.yml → tag v0.32.1 + GitHub release + Sigstore provenance → dispatches publish.yml → npm publish via OIDC trusted publishing.
askalf
enabled auto-merge (squash)
July 29, 2026 20:25
sprayberry-reviewer
approved these changes
Jul 29, 2026
sprayberry-reviewer
left a comment
sprayberry-reviewer
left a comment
Collaborator
There was a problem hiding this comment.
Automated review from the Sprayberry Labs fleet code reviewer.
Verdict: No blocking issues found — clean release PR.
This is a version-bump/release PR only: CHANGELOG.md gains the [0.32.1] entry, and package.json/package-lock.json are bumped from 0.32.0 to 0.32.1 in lockstep. The actual behavioral fix (#186, the citation-disclaimer bug) already landed in #191 — this PR touches no source code.
What I checked:
package.jsonandpackage-lock.jsonversions match (0.32.1in both places) — no lockfile drift.- CHANGELOG entry accurately describes the shipped fix and correctly notes it's additive (
disclaimersfield, no API break). - CI check-rollup is all green:
build (20),build (22),CodeQL,actionlintall SUCCESS. - No test coverage concerns — no logic changed in this diff.
Nothing to request changes on.
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
2 participants
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.
release: 0.32.1
Ships the #186 fix (merged in #191): a source-disclaimer sentence no longer
counts its bracketed ids as unsupported citations, so being transparent about
discarded sources stops costing the answer its supportRatio.
Patch, not minor — no API change.
VerificationReportgains an additivedisclaimersfield; the only consumers (agent.ts, cli.ts) read.unsupported.Verified before opening: extract-release-notes.cjs resolves the new
## [0.32.1]section (empty release notes was the #135 failure mode),package-lock version tracks package.json at 0.32.1, typecheck clean,
859 tests / 0 failures.
Merging this fires auto-release.yml → tag v0.32.1 + GitHub release + Sigstore
provenance → dispatches publish.yml → npm publish via OIDC trusted publishing.