Release: prepare v1.5.1 reliability candidate - #1061
Conversation
![gitar-bot[bot]](https://avatars.githubusercontent.com/in/827041?s=60&v=4){kind=small}
|
|
||
| ## 1.5.1 — release | ||
|
|
||
| Cross-provider installation, audit provenance, safe initialization, remote-observer diagnostics, and Board/status clarity. See [release notes](docs/v151-release-notes.md) and the [qualification contract](docs/v151-qualification.md). |
There was a problem hiding this comment.
⚠️ Bug: CHANGELOG rewrites already-published v1.5.0 release text
CHANGELOG.md's ## 1.5.1 — release heading is new, but the diff also edits the pre-existing ## 1.5.0 — release section, changing "remain v1.5.1. Audit publication binds the current head reliably (#1025)." to "remain v1.6.0." This section documents the already-published v1.5.0 release. The project's own rule, stated in docs/pypi-release.md ("Editing main cannot repair that tagged README or the README embedded in its package. Never rewrite a published tag to correct the wording."), and echoed in README.md's example about immutable candidate text, forbids retroactively editing text that shipped in a prior release. Rewriting the v1.5.0 changelog entry to reflect a later roadmap decision (Slack telemetry deferred to v1.6.0 instead of v1.5.1) corrupts the historical record of what v1.5.0 actually stated at release time. The correct fix is to leave the v1.5.0 section's original wording untouched and only state the updated deferral target in the new v1.5.1 section/current-facing docs.
Revert the edit to the historical v1.5.0 entry and only reflect the v1.6.0 deferral in current-facing text (already updated in docs/current-state-and-roadmap.md and the new v1.5.1 release notes).:
- Explicit `slack setup` hosted manifest and redacted `slack doctor` (#1024).
Default install remains Slack-free. Offline snapshots never prove live readiness.
Basic private-workspace interaction only; telemetry/Board links and rich UX
remain v1.5.1. Audit publication binds the current head reliably (#1025).
Was this helpful? React with 👍 / 👎
| #1037 and its fixed Slack callback boundary. Follow the | ||
| the reviewed final release preparation PR. For v1.5.1 that head must include | ||
| the five reliability revisions tracked by #1050. Follow the | ||
| [immutable release text gate](pypi-release.md#immutable-release-text-gate-v150-onward): |
There was a problem hiding this comment.
💡 Quality: Stale #1037/v150 anchor left after v1.5.1 identity update
docs/public-release-checklist.md:143 was edited in this PR (from referencing #1037 to "the five reliability revisions tracked by #1050") but the accompanying link on the same line still points to pypi-release.md#immutable-release-text-gate-v150-onward, an anchor derived from a v1.5.0-era heading that no longer matches any heading text in docs/pypi-release.md (there is no heading that slugifies to immutable-release-text-gate-v150-onward). Since this exact paragraph was touched to update v1.5.0→v1.5.1 identity, the dangling anchor should have been corrected or removed in the same edit.
Point the link at the actual heading/anchor in pypi-release.md, or drop the anchor fragment and link to the file itself.:
[immutable release text gate](pypi-release.md):
Was this helpful? React with 👍 / 👎
|
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
|
| Compact |
|
Was this helpful? React with 👍 / 👎 | Gitar
Claude audit (merge-authority lane)Head SHA: |
Claude audit (merge-authority lane)Head SHA: |
1 participant
Problem and resulting behavior
The five v1.5.1 reliability revisions are merged, but the public release identity, candidate workflow, install docs, and qualification contract still target v1.5.0. This PR prepares one immutable v1.5.1 candidate from the eventual merge SHA and makes current-facing guidance consistently use the v1.5.1 path.
It records the v1.5.1 release notes, qualification contract, and ordered candidate-first publication runbook; updates package and public documentation identity to 1.5.1; binds CI and the candidate workflow to the v1.5.1 rehearsal; and keeps Slack telemetry explicitly scheduled for v1.6.0.
Part of #1056 and the #1050 roadmap epic.
Included reliability revisions
Validation
pytest -q: 5,046 passed, 18 skipped, 5 stale v1.5.0 assertions identified and corrected; the affected release/documentation suite then passed with 444 tests and 1,288 subtestsgit diff --check: passeddoc_ref, 1.4.2 upgrade, rollback, and uninstall state preservationLive Slack evidence, the bounded hosted Board canary, exact merge-SHA candidate qualification, PyPI publication, GitHub Release creation, and the final codemower.com upload remain post-merge release gates.