From 853d02d48d7794054b9223bee0b59cc69b8d1294 Mon Sep 17 00:00:00 2001 From: Daniele Favara Date: Fri, 21 Aug 2026 11:14:45 +0200 Subject: [PATCH] docs: document release PR recovery --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index af63965..b182aeb 100644 --- a/README.md +++ b/README.md @@ -98,7 +98,9 @@ Release Please owns the repository version. Conventional commits drive version b When the Release Please PR is merged, the same release workflow creates the GitHub release and publishes both the versioned container image and the Helm chart to GHCR. -A release PR must retain Release Please's `autorelease: pending` metadata. If a PR has to be recreated manually from the generated release branch, restore that label before merging it; otherwise Release Please will treat the merge as an ordinary commit and generate the next release proposal instead of tagging the merged version. +A release PR must retain Release Please's `autorelease: pending` metadata. If a PR has to be recreated manually from the generated release branch, restore that label and preserve the generated Release Please body/header before merging it; otherwise Release Please may treat the merge as an ordinary commit and generate the next release proposal instead of tagging the merged version. + +For recovery of a merged-but-untagged release PR, restore `autorelease: pending`, repair the generated body if needed, and re-run the Release Please workflow before accepting a newer release proposal. ## Roadmap