Describe the bug
Codeowners can edit README.md content outside the Release Information block on a release-review/* branch during release review. Those edits merge into the release snapshot/tag but are lost afterward — the post-release sync PR only splices the <!-- CAMARA:RELEASE-INFO:START -->/END block back into main, so anything else is silently dropped.
To Reproduce
- Open a release review PR against a
release-review/rX.Y-* branch.
- Push an edit to README.md outside the Release Information block (e.g. the Scope section).
- Merge into the release-review branch; tag the release.
- Check the post-release sync PR to
main — the edit is absent.
Surfaced on NetworkAccessManagement r3.1: camaraproject/NetworkAccessManagement#169 merged such an edit into the r3.1 snapshot/tag; camaraproject/NetworkAccessManagement#170 (the post-release sync PR) does not carry it. Caught by a reviewer comment, not by automation.
Expected behavior
Take README.md out of scope of the release-review PR/branch. Codeowners make README changes on main like any other content change, not on the release-review branch. The Release Information block stays the only automated README change during the release process, synced at snapshot creation and again in the post-release sync PR.
Additional context
Decided on the 2026-07-29 CAMARA Release Management call: remove README.md from Release Review PR scope; keep the delimiter-block sync in the post-release sync PR only.
Root cause: release-automation-reusable.yml's "Create Post-Release Sync PR" job only extracts the delimited Release Information block from the tag (same pattern as readme_updater.py). Nothing currently restricts codeowners to editing only that block on the release-review branch.
A PR implementing this will follow.
Describe the bug
Codeowners can edit README.md content outside the Release Information block on a
release-review/*branch during release review. Those edits merge into the release snapshot/tag but are lost afterward — the post-release sync PR only splices the<!-- CAMARA:RELEASE-INFO:START -->/ENDblock back intomain, so anything else is silently dropped.To Reproduce
release-review/rX.Y-*branch.main— the edit is absent.Surfaced on NetworkAccessManagement r3.1: camaraproject/NetworkAccessManagement#169 merged such an edit into the r3.1 snapshot/tag; camaraproject/NetworkAccessManagement#170 (the post-release sync PR) does not carry it. Caught by a reviewer comment, not by automation.
Expected behavior
Take README.md out of scope of the release-review PR/branch. Codeowners make README changes on
mainlike any other content change, not on the release-review branch. The Release Information block stays the only automated README change during the release process, synced at snapshot creation and again in the post-release sync PR.Additional context
Decided on the 2026-07-29 CAMARA Release Management call: remove README.md from Release Review PR scope; keep the delimiter-block sync in the post-release sync PR only.
Root cause:
release-automation-reusable.yml's "Create Post-Release Sync PR" job only extracts the delimited Release Information block from the tag (same pattern asreadme_updater.py). Nothing currently restricts codeowners to editing only that block on the release-review branch.A PR implementing this will follow.