Make a release with a Makefile target - #12
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
1 participant
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.
The bump workflow needed a signed commit, but a workflow cannot sign one with your key. A local target is simpler and it keeps the signature.
make release VERSION=x.y.zruns the linter and the tests, creates the branchrelease/vx.y.z, raises the version inmagit-standup.eland inEaskfile, and commits. You push the branch and open a pull request. The publish workflow makes the tag and the release after you merge it.The workflow
release-prepare.ymlis removed. The workflowrelease.ymlstays as it is.A new label
releasemarks a version bump. The changelog configuration excludes that label, so a bump does not appear in the release notes.The README has a new
Releasesection.