Part of #706 (close remaining release-process automation gaps).
Gap
When openemr/openemr cuts a release tag, the conductor emits openemr-tag to website-openemr. The release-docs workflow regenerates the release-docs/<version> PR and flips the rendered page banner DRAFT → FINAL by writing status: FINAL into data/releases.json (via ReleasesManifest::applyTag). That part is automated and works.
What is not automated: the release-docs/<version> PR is opened as a GitHub draft (gh pr create --draft in the workflow:upsert-pr task) and is never marked ready or merged. After the tag lands, an operator has to manually mark the docs PR ready and merge it to publish the now-FINAL pages. The conductor and infra PRs are merged by the ship flow; the website docs PR is the one manual leg.
Desired
On openemr-tag only — once the FINAL content is pushed and checks are green — automatically mark the release-docs/<version> PR ready and merge it. Either as a leg of the ship-release workflow, or via a finalize step in the website-openemr release-docs workflow.
Notes
Part of #706 (close remaining release-process automation gaps).
Gap
When
openemr/openemrcuts a release tag, the conductor emitsopenemr-tagtowebsite-openemr. The release-docs workflow regenerates therelease-docs/<version>PR and flips the rendered page banner DRAFT → FINAL by writingstatus: FINALintodata/releases.json(viaReleasesManifest::applyTag). That part is automated and works.What is not automated: the
release-docs/<version>PR is opened as a GitHub draft (gh pr create --draftin theworkflow:upsert-prtask) and is never marked ready or merged. After the tag lands, an operator has to manually mark the docs PR ready and merge it to publish the now-FINAL pages. The conductor and infra PRs are merged by the ship flow; the website docs PR is the one manual leg.Desired
On
openemr-tagonly — once the FINAL content is pushed and checks are green — automatically mark therelease-docs/<version>PR ready and merge it. Either as a leg of the ship-release workflow, or via a finalize step in the website-openemr release-docs workflow.Notes
release-docs/8.1.0regenerated correctly but stayed a draft requiring a hand merge.openemr/openemrdocs/RELEASE_PROCESS.md(PR docs: add end-to-end RELEASE_PROCESS.md for automated release flow openemr#12117).