Skip to content

v0.13.1 — lossless finding titles

Choose a tag to compare

View all tags
@Rynaro Rynaro released this 30 Jul 22:42
· 38 commits to main since this release
v0.13.1
29e06cb
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's fixed

Inline review-comment titles are no longer cut mid-word at 120 characters (#35) — the recurring truncated-title reports:

  • Titles end at a sentence or word boundary, with a visible … when truncated; whitespace-normalized to a single line; UTF-16 surrogate-pair-safe at every cut (no � on GitHub).
  • Zero information loss: when a title is truncated, the full provider message is preserved as the first paragraph of the comment body.
  • The shared prompt now instructs all providers (Anthropic / OpenAI / Copilot) that message is a one-line headline (≤ ~100 chars) with detail belonging in rationale — so truncation rarely triggers at all.
  • Whitespace-only provider messages are rejected with reason_code: blank_message instead of producing an empty title.
  • FINDING_TITLE_MAX_LENGTH = 120 is now exported from @prisma-bot/shared and machine-enforced on NormalizedFinding.title.

819 tests across 52 files, all passing · 15/15 deterministic eval scenarios PASS (report byte-identical — no behavior change for in-cap titles).

Full Changelog: v0.13.0...v0.13.1

🤖 Generated with Claude Code

Assets 2
Loading