chore(main): release 1.3.0 - #2428
Conversation
e2fbd47 to
4b9a4cc
Compare
Automated Status SummaryHead SHA: 0051d68
Updated automatically; will refresh on subsequent CI/Docker completions. Keepalive checklistScopeDoc-rot was the audit's most pervasive defect class (most of §1/§4 findings were stale docs). Tasks
Acceptance criteria
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4b9a4cc639
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| * harden synced metrics parser ([4590511](https://github.com/stranske/Workflows/commit/459051114fd11b1a930ea04d0344e69dbad7f359)) | ||
| * harden synced runner helpers ([#2044](https://github.com/stranske/Workflows/issues/2044)) ([2e359bb](https://github.com/stranske/Workflows/commit/2e359bbf806cd2871d608dc10475e3b2d2d81dcb)) | ||
| * harden tracker matching and eligibility checkout ([#2121](https://github.com/stranske/Workflows/issues/2121)) ([40d5594](https://github.com/stranske/Workflows/commit/40d5594478a15aaa02c86d80d17ab5a243b0a7c6)) | ||
| * **health-74:** re-baseline 7 stale template-drift allowlist entries ([#2397](https://github.com/stranske/Workflows/issues/2397)) ([f6378d5](https://github.com/stranske/Workflows/commit/f6378d53a36192ee1a17c9588be7c67a5b5df18c)) |
There was a problem hiding this comment.
This release commit is for 1.3.0, but the only new note is appended inside the existing 1.2.0 section while .release-please-manifest.json remains at 1.2.0; I checked .github/workflows/maint-61-release-please.yml, which runs release-please with that manifest file. After this lands, the next main push will still see 1.2.0 as current and can keep proposing/releasing the same post-1.2 change instead of recording v1.3.0; this entry should be under a new 1.3.0 heading with the manifest bumped in the same release commit.
Useful? React with 👍 / 👎.
|
Gate fast-pass: docs-only change detected; heavy checks skipped. |
GitHub Actions
Failure
1 participant
Closes #2367
Automated Status Summary
Scope
Doc-rot was the audit's most pervasive defect class (most of §1/§4 findings were stale docs).
maint-66's monthly audit only carries a static "update docs" checklist; nothing systematically detects drift. This closes that gap on a monthly cadence.Tasks
Acceptance criteria
EXPECTED_NAMES+ both inventory docs;tests/workflows/green (24 passed).persist-credentials: false, scopedissues: write.[Docs Drift Audit]issue at a time.Head SHA: 4b9a4cc
Latest Runs: ✅ success — Gate
Required: gate: ✅ success