Add automated release workflow with release-plz#3
Merged
Conversation
Adds release-plz configuration and GitHub Actions workflow for automated crates.io publishing via trusted publishing (OIDC). On push to main, release-plz creates a release PR with version bumps and changelogs. When the release PR is merged, it publishes crates in dependency order (libudx -> peeroxide-dht -> peeroxide) and creates GitHub releases with tags.
89f461e to
05af7d8
Compare
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
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.
Summary
Adds automated crates.io publishing via release-plz with trusted publishing (OIDC — no API token needed).
release-plz.toml— workspace config with version groups, semver checks, and changelog generation.github/workflows/release.yml— two-job GitHub Actions workflow (Release PR + Publish)How It Works
On every push to
main:libudx→peeroxide-dht→peeroxide) and creates GitHub releases with tagsConfiguration Choices
release_alwaysfalseversion_grouppeeroxidegroupsemver_checktruegit_release_enabletrueSetup Required
After merging, configure trusted publishing on crates.io for each crate:
peeroxide-dhtandpeeroxide)Rightbracketpeeroxiderelease.ymlThat's it — all future releases are fully automated with no tokens.
Release Flow
main(via merged PRs)