fix(ci): restore release-please parsing and latest action (#113)

## Summary

- restore the latest Release Please action v5.0.0
- reject Markdown bullets in commit override blocks, matching the
upstream parser contract
- correct the repository instructions and add regression coverage
- recover the incomplete v0.22.2 GitHub Release and lifecycle labels
- correct the merged override blocks on PRs #108 and #110

## Validation

- `PYTHONPATH=. pytest -q tests/tier1_unit/test_validate_repo.py` (5
passed)
- `python scripts/validate_repo.py`
- `git diff --check`
- workflow YAML parsed successfully

BEGIN_COMMIT_OVERRIDE
fix(ci): restore release-please parsing and latest action

docs: correct Release Please commit override syntax
END_COMMIT_OVERRIDE

Author: nmorgowicz

.github/workflows/release-please.yml

@@ -25,7 +25,7 @@ jobs:
           client-id: ${{ vars.GH_APP_CLIENT_ID }}
           private-key: ${{ secrets.GH_APP_PRIVATE_KEY }}
 
-      - uses: googleapis/release-please-action@5c625bfb5d1ff62eadeeb3772007f7f66fdcf071 # v4.4.1
+      - uses: googleapis/release-please-action@45996ed1f6d02564a971a2fa1b5860e934307cf7 # v5.0.0
         with:
           token: ${{ steps.app-token.outputs.token }}
           config-file: .github/release-please/config.json5

AGENTS.md

@@ -240,16 +240,20 @@ So user-facing changes need a `feat:` or `fix:` title.
 Every implementation PR body must include a Release Please override block using this exact format:
 
 - Each line is one Conventional Commit entry.
-- Format: `- type(scope): description`
-- The leading `- ` is required.
+- Format: `type(scope): description`
+- Do not prefix entries with Markdown bullets. Release Please parses the block as a
+  commit message, so a leading `- ` makes the entry invalid.
 
 Example:
 
 ```text
 BEGIN_COMMIT_OVERRIDE
-- fix(model): correct seed max from 2^63-1 to 2^32-1
-- docs: restore advanced env var detail in .env.example and HOW_TO_RUN.md
+fix(model): correct seed max from 2^63-1 to 2^32-1
+
+docs: restore advanced env var detail in .env.example and HOW_TO_RUN.md
 END_COMMIT_OVERRIDE
 ```
 
-One Conventional Commit line per entry; one supported type per entry; no composite headers. Release Please version PRs are exempt. Keep model artifacts and benchmark audio out of PRs.
+One Conventional Commit line per entry; separate multiple entries with a blank line; one
+supported type per entry; no composite headers. Release Please version PRs are exempt.
+Keep model artifacts and benchmark audio out of PRs.

scripts/validate_repo.py

@@ -27,7 +27,7 @@
     "revert",
 )
 OVERRIDE_ENTRY_RE = re.compile(
-    rf"^-? ?({'|'.join(CONVENTIONAL_TYPES)})(?:\([a-z0-9][a-z0-9._/-]*\))?!?: .+$"
+    rf"^({'|'.join(CONVENTIONAL_TYPES)})(?:\([a-z0-9][a-z0-9._/-]*\))?!?: .+$"
 )
 
 
@@ -47,7 +47,7 @@ def validate_pr_override_body(body: str) -> None:
     if invalid:
         raise RuntimeError(
             "Release Please override entries must each be a single Conventional Commit line "
-            "with one supported type and an optional simple scope; "
+            "without a Markdown list marker, with one supported type and an optional simple scope; "
             f"invalid entries: {invalid}"
         )
 

tests/tier1_unit/test_validate_repo.py

@@ -41,5 +41,14 @@ def test_accepts_entries_without_blank_line_separators(self):
 """
         )
 
+    def test_rejects_markdown_list_markers(self):
+        with pytest.raises(RuntimeError, match="without a Markdown list marker"):
+            validate_pr_override_body(
+                """BEGIN_COMMIT_OVERRIDE
+- fix(runtime): do not pass a list item to the commit parser
+END_COMMIT_OVERRIDE
+"""
+            )
+
     def test_ignores_bodies_without_an_override(self):
         validate_pr_override_body("Renovate dependency update")