Repository navigation
ci: generate release notes on a release tag - #21
Merged
Merged
Conversation
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
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.
Adds the trigger-only shim for the org-wide release-notes reusable workflow
(krateo-platformops/.github). On any N.N.N tag push it generates release notes from the commit log
and publishes them to the GitHub Release body and this org's release-feed.
The workflow itself lives once in krateo-platformops/.github, so "identical across every repo" stays
structural rather than a copy each repo has to keep in step. This file supplies only the triggers.
It is top-level rather than a job inside release-oci because a called workflow's permissions are
capped at its caller's (the release shims pin
contents: read) and custom secrets are not inheriteddown a nested call, so a nested job could neither write the release body nor see the credential.
Notes can never fail a release: every sink is guarded independently, and a missing or expired
credential skips the job with a warning rather than a red tick.
Already live and verified on installer, frontend and alert-troubleshooter.