ci: automatically publish release notes to GitHub Releases #643
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
This branch adds a GitHub Actions workflow to automatically publish release notes to GitHub Releases when a tag is pushed on the `master` branch that corresponds to a release. The release notes are parsed from the changelog using taiki-e/create-release-action. The workflow will only run when a tag matching `tower-[0-9].+` or `tower-[a-z]+-[0-9].+` is pushed to the `master` branch on the origin (`tower-rs/tower`) repo.
davidpdrsn
approved these changes
Feb 16, 2022
|
@davidpdrsn for the record, all this does is create a GitHub Release from a tag; my experience is that it's easy to forget to do that, so it's nice to automate that step. |
|
(and, if it fails for any reason, the GitHub release can still be created manually) |
|
Ah yes true. All good! |
hawkw
added a commit
that referenced
this pull request
Feb 16, 2022
In #643, I accidentally included a `v` before the version number in the regex for matching release tags for the `tower` crate, but not for `tower-whatever` crates. All previous release tags on this repo don't use a `v`, so adding it was a mistake. This branch removes it.
hawkw
added a commit
that referenced
this pull request
Feb 16, 2022
In #643, I accidentally included a `v` before the version number in the regex for matching release tags for the `tower` crate, but not for `tower-whatever` crates. All previous release tags on this repo don't use a `v`, so adding it was a mistake. This branch removes it.
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 branch adds a GitHub Actions workflow to automatically publish
release notes to GitHub Releases when a tag is pushed on the
masterbranch that corresponds to a release.
The release notes are parsed from the changelog using
taiki-e/create-release-action. The workflow will only run when a tag
matching
tower-[0-9].+ortower-[a-z]+-[0-9].+is pushed to themasterbranch on the origin (tower-rs/tower) repo.