Release Code Mower v1.1.0 with opt-in Jira Cloud support - #815
Conversation
|
Note Automatic reviews are paused because your team has used its included automatic processing for this billing period (headroom scales with your seat count). You can still comment "Gitar review" to run one anytime, and automatic reviews resume on their own by October 1. Add seats for more headroom. Code Review ✅ ApprovedRelease v1.1.0 adds opt-in Jira Cloud support with read-only adoption, double-gated writes, and PR-to-Jira synchronization, while keeping GitHub authoritative. Comprehensive test coverage across full suite, Jira-focused tests, and release hygiene with all 14 readiness checks passing. No issues found. OptionsDisplay: compact → Showing less information. Comment with these commands to change the behavior for this request:
Was this helpful? React with 👍 / 👎 | Gitar |
Claude audit (merge-authority lane)Head SHA: Claude Audit: PASS Summary: This is a release-bump PR (v1.0.15 -> v1.1.0) touching pyproject.toml, init.py, docs, and workflow templates, plus a matching test_release_hygiene.py update and a new docs/v11-release-notes.md. Version strings, package specs, and release-tag references are updated consistently across all touched files, both packaged template copies (src/code_mower/templates and templates/) were updated identically, and the new release-notes doc and README link were added in lockstep with the corresponding test assertions. No security, data-loss, or broken-contract issues found. Findings: none. |
Closes #801.
Summary
PR-to-Jira synchronization, provider fixes, and the metadata-only boundary
Verification
No live Jira mutation was authorized or attempted.
CODE_MOWER_BUILDER:codex