From 2e5ecb00d754aa22bcd7ed767254a79e5ecd16ef Mon Sep 17 00:00:00 2001 From: Daniele Favara Date: Fri, 21 Aug 2026 11:13:04 +0200 Subject: [PATCH] docs: document release-please PR metadata --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 09f1501..af63965 100644 --- a/README.md +++ b/README.md @@ -98,6 +98,8 @@ 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. + ## Roadmap 1. Validate the pinned Web Client baseline and OCI release pipeline.