The README (Updates), docs/CLI.md, ADR 0009, the header of the threat model and a comment in Directory.Build.props say 1.2.0 where they said 1.1.1.
Why
Closes#218. There is no release numbered 1.1.1 (owner's decision, #200). docs/RELEASING.md is left to the work on #197.
How it was tested
Documents and one comment only. Gates from PowerShell without the UI suite: build with warnings as errors, both test suites, line coverage 100%, format clean.
Checklist
Commits are signed and signed off (git commit -S -s)
Zero build warnings; format and lint are clean
Tests added or updated; the 100% coverage gate still passes (no code changed)
Docs updated for user-visible changes; threat model updated if the attack surface changed
No secrets, credentials, or personal data
New dependencies are justified below, or none were added (none)
Substantial AI assistance, if any, is noted here: written with Claude Code.
## What
The README (Updates), docs/CLI.md, ADR 0009, the header of the threat model and a comment in Directory.Build.props say 1.2.0 where they said 1.1.1.
## Why
Closes #218. There is no release numbered 1.1.1 (owner's decision, #200). docs/RELEASING.md is left to the work on #197.
## How it was tested
Documents and one comment only. Gates from PowerShell without the UI suite: build with warnings as errors, both test suites, line coverage 100%, format clean.
## Checklist
- [x] Commits are signed and signed off (`git commit -S -s`)
- [x] Zero build warnings; format and lint are clean
- [x] Tests added or updated; the 100% coverage gate still passes (no code changed)
- [x] Docs updated for user-visible changes; threat model updated if the attack surface changed
- [x] No secrets, credentials, or personal data
- [x] New dependencies are justified below, or none were added (none)
- [x] Substantial AI assistance, if any, is noted here: written with Claude Code.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
There is no release numbered 1.1.1: the fixes planned for it and Gitea
support go out together as 1.2.0 (owner's decision, #200). The README, the
CLI guide, ADR 0009, the header of the threat model and a comment in
Directory.Build.props still named 1.1.1.
docs/RELEASING.md is left to the work on the release pipeline (#197).
Closes#218
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Signed-off-by: James Maes <james@kof22.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
The README (Updates), docs/CLI.md, ADR 0009, the header of the threat model and a comment in Directory.Build.props say 1.2.0 where they said 1.1.1.
Why
Closes #218. There is no release numbered 1.1.1 (owner's decision, #200). docs/RELEASING.md is left to the work on #197.
How it was tested
Documents and one comment only. Gates from PowerShell without the UI suite: build with warnings as errors, both test suites, line coverage 100%, format clean.
Checklist
git commit -S -s)🤖 Generated with Claude Code