Skip to content

v0.10.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 14 Aug 21:26
· 6 commits to main since this release
v0.10.0
d8db042
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

umactually v0.10.0

Fixes the Minimax-M3 failure mode that degraded waffle-house-menu PR #77's second review.

Fixed

  • Findings with provider-empty `body` are no longer posted as `Finding at :.` placeholders. When every inline finding body is empty, the self-healing retry now fires on the empty-body condition (previously it only fired on parse failure), the parser accepts the common body-key aliases `description`, `message`, `comment`, `issue`, and `detail` (the v0.9.2 schema rejected any key other than the literal `body`), and findings that are still empty after the retry are suppressed with full disclosure (suppressed count, per-finding `parse-warnings.json` entries, the new `empty-body` audit reason, and a `::notice::` line on the step summary) instead of being posted as location-only inline threads.
  • `docs/configuration.md` documented a nonexistent `UMACTUALLY_DEBUG_RAW_RESPONSE` env var; corrected to `UMACTUALLY_DEBUG_RAW` with the GitHub Actions job-env workaround.

Why a minor bump

The default behavior of the inline-comment posting path changes: previously, an empty-body finding would be posted as a placeholder; now it is suppressed. The new behavior is fully backward-compatible for valid reviews (any review with at least one populated body is unaffected). The `parse-warnings.json` artifact gains an additive `empty-body` reason key. Per `docs/release-process.md:69-73`, this is a minor.

Full Changelog

See CHANGELOG.md.

Assets 8
Loading