// changelog
v0.5.0
Scope expansion. Every review scope advertised in `list` works end-to-end; JSON output locked at schema v1.
Released May 19, 2026
Added
--commit <hash>review scope with merge-commit handling: when the requested hash has two or more parents, the diff is taken against the first parent only and a stderr warning suggests--pull-request <target>...<feature>for full branch comparison.--branch <target>and--pull-request <target>...<feature>review scopes — backend was already wired; this release adds the integration test coverage.- Mutually exclusive scope flags. Passing two scope flags at
once (
--staged --unstaged) fails before the pipeline runs. lang.SourceCLIFlag— newSourceenum value so--langoverrides are attributed correctly in dry-run output instead of being mislabeledSourceRepoConfig.- Drift-guard golden test for
--jsonoutput. Byte-exact fixture atinternal/render/testdata/json/v1.golden; any rename, type change, or removal trips the test.
Changed
- CLI user-facing strings routed through
i18n.Catalog.T(). Sixteen new keys cover the action paths (init, review, compress, setup); Turkish translations ship for every key.%werror wrappers and tabular dry-run output stay English by design. - JSON schema v1 policy documented. Additive changes are not a
version bump; renames, removals, or type changes require schema
version 2 + a CHANGELOG entry. Shape unchanged from v0.4.0:
{schema, content, findings, summary, meta}.
Fixed
- Windows golden-file test now passes regardless of
core.autocrlf—.gitattributespins text files to LF in the working tree.