feat: allow release name template through env var#131
Merged
Conversation
stipsan
approved these changes
Feb 4, 2026
Member
stipsan
left a comment
stipsan
left a comment
There was a problem hiding this comment.
Looks good to me, I'm not aware of a better way to handle this
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
2 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.
Description
Have a use case where I want to override the release title to use
nextRelease.versioninstead ofnextRelease.name. Would be ideal not to have to eject from the preset just to do so.CI linter complained about not using
standardfor formatting - not sure how that has passed previously, but this also does astandard --fix.What to review
Are there better ways of doing this?
Testing
Untested, but change seems fairly trivial?