Goal
Automate updates for the release notes published in cf-docs so upstream changes produce small, reviewable PRs instead of manual copy work.
Target issues
Acceptance criteria
- Each target has a repeatable refresh command or workflow, or a documented reason automation is not viable.
- Automation opens or updates a PR only when the published output changes.
- PRs identify the upstream source version/revision and affected page.
- Existing published routes and frontmatter are preserved.
Out of scope
- Rewriting release-note content beyond mechanical formatting needed for publication.
- Automating the Release Notes index, Release History, or Weekly Patch Releases pages unless a target needs link updates there.
Goal
Automate updates for the release notes published in cf-docs so upstream changes produce small, reviewable PRs instead of manual copy work.
Target issues
Acceptance criteria
Out of scope