doc: list release artifacts produced by the release procedure#10676
Open
armru wants to merge 2 commits into
Open
doc: list release artifacts produced by the release procedure#10676armru wants to merge 2 commits into
armru wants to merge 2 commits into
Conversation
dosubot
Bot
added
the
size:M
cnpg-bot
added
backport-requested ◀️
Contributor
|
❗ By default, the pull request is configured to backport to all release branches.
|
armru
changed the title
armru
added
do not backport
mnencia
pushed a commit
that referenced
this pull request
May 14, 2026
- Move OLM bullet from "Per released version" to "Produced once per release cycle" (OLM artifacts are only built for the latest/RC version) - Add missing artifacts: Krew plugin manifest and `cloudnative-pg/artifacts` repo as OLM bundle destination - Fix pre-existing typo: `.github/ISSUE_TEMPLATES/` -> `.github/ISSUE_TEMPLATE/` Targets #10676 Signed-off-by: Gabriele Quaresima <gabriele.quaresima@enterprisedb.com>
mnencia
added
backport-requested ◀️
Add a "Release artifacts" section to contribute/release_procedure.md that summarises what a complete run of the procedure produces, split between per-version artifacts (GitHub release, container images, OLM bundle and catalog with the community-operators PR, supply-chain attestations — cosign signatures, Sigstore bundles, SBOMs, SLSA provenance — and updated docs) and artifacts produced once per release cycle (announcement, Helm chart, bug.yml versions, cloudnative-pg/api tag). This gives maintainers a checklist to confirm a release is complete. Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com>
- Move OLM bullet from "Per released version" to "Produced once per release cycle" (OLM artifacts are only built for the latest/RC version) - Add missing artifacts: Krew plugin manifest and `cloudnative-pg/artifacts` repo as OLM bundle destination - Fix pre-existing typo: `.github/ISSUE_TEMPLATES/` -> `.github/ISSUE_TEMPLATE/` Targets #10676 Signed-off-by: Gabriele Quaresima <gabriele.quaresima@enterprisedb.com>
mnencia
force-pushed
the
docs/release-procedure-artifacts
branch
from
a784d5f to
24b2a18
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a "Release artifacts" section to contribute/release_procedure.md that summarises what a complete run of the procedure produces, split between per-version artifacts (GitHub release, container images, OLM bundle and catalog with the community-operators PR, supply-chain attestations — cosign signatures, Sigstore bundles, SBOMs, SLSA provenance — and updated docs) and artifacts produced once per release cycle (announcement, Helm chart, bug.yml versions, cloudnative-pg/api tag). This gives maintainers a checklist to confirm a release is complete.