Add a template for new releases #178
Merged
Conversation
This file contains 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
Signed-off-by: Ben Cotton <ben@kusari.dev>
SecurityCRob
approved these changes
Feb 4, 2025
eddie-knight
approved these changes
Feb 11, 2025
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.
Creates an issue type that we can use as a checklist when we cut a new release. It lists all the steps so that we do it right every time.
Open question: do we want to also tag the repo? I don't think it particularly matters here and since I'm not quite sure how GitHub handles tags with protected branches, I decided to leave it out. However, if someone feels strongly that tagging the repo is important, I'm willing to have that discussion. My argument against is that no one will consume this via the repo, just from the website, so the fact that we have published versions obviates the need for a git tag.
If you want to see this in action, https://github.com/funnelfiasco/security-baseline/issues/new?template=release.yaml