Adding a simple crates.io release workflow, including MSRV check #9
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
…ed version validation.
daemontus
force-pushed
the
daemontus/feat/release-ci
branch
from
48cb87d to
1dbeb05
Compare
Collaborator
Author
|
I tested the release workflow on a |
Collaborator
|
The new build process LGTM. I also tested the versions on crates.io, they work fine. Would you mind adding the tags of the form Then we could follow the upstream naming for release candidates (and potentially already release versions for the two release candidates hopefully soon) |
Collaborator
Author
|
Good idea :) Done and merging! |
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.
This should allow everyone in
cuddorgto release new versions ofcudd-syssimply by creating a new tag/release in the repository (the tag must follow thev*.*.*,v*.*.*-alpha.*, orv*.*.*-beta.*format).