ci: Add release checks and jobs #42
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
jrobsonchase
force-pushed
the
josh/nix/semver-checks
branch
7 times, most recently
from
2d341a5
to
17f4d6e
Compare
jrobsonchase
force-pushed
the
josh/nix/semver-checks
branch
from
d204240
to
493244d
Compare
jrobsonchase
changed the title
bobzilladev
approved these changes
Jan 24, 2023
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.
Alright, I'm reasonably happy with this now. Semver checks now happen before PR merge, and once it hits master, it'll always try to publish, and if the publish succeeds, it'll add a git tag for us.
So all we have to do to publish is make a PR with a version bump!