Repository navigation
chore(release): cut a release with cog bump - #49
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.
cog.toml:cog bumpon achore/release-*branch runstools/release-prepare, commitschore(version): X.Y.Zand tags that commit. cog writes no changelog; towncrier does, in the hook.tools/release-prepare NEW:towncrier build, then the version inbuild.zig.zon,src/main.zig, the README and two documentation pages. Each edit goes throughset_in, which refuses a file the expression leaves unchanged, so a version string that moved stops the bump. The header lists what the script sets and the prose it leaves to a person.RELEASING.md: the steps aroundcog bump.Checked
tools/release-preparerun against this tree for the next minor version, the diff read, and the tree put back.shellcheckis clean on the script. No release is cut here.Closes #48