Configure publishing for a new release #63
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
|
To make the new publishing work, we'll want to add a trusted publisher to the meza project. @reubano Can you do that? The workflow name is After configuring that and merging this PR, we should be able to tag the commit and GitHub will create the release automatically. This is my first time implementing trusted publishing, so there may be some bumps, but I'll work through them and let you know if I need any help. |
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.
Configure the project for trusted publishing of tagged commits.
Bump version for next release
Add Jason as a maintainer.
Cleaned up some legacy details from docs.
Configure meza for trusted publishing.