Add workflow to publish from tags #68
Open
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
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.
To enable this workflow you need to generate a login token and store that as a secret here in github. You can generate such a token by logging into crates.io and navigating to https://crates.io/me.
The name of the secret must be
CRATES_TOKEN.When all of that is done, you can push a tag that matches the version inside the
Cargo.toml, e.g.: v0.1.0 and the script should automatically start the publishing process.Currently this uses quite a simple approach, as there's currently only one crate to deploy. Later on, if we add more crates, it would probably better to group crates into a workspace and use tools to manage version bumps and branching. But it should be quite simple to change to that later on.