Skip to content

Add release-plz workflow for automated releases#34

Open
nichmor wants to merge 1 commit intomainfrom
feat/release-plz-workflow
Open

Add release-plz workflow for automated releases#34
nichmor wants to merge 1 commit intomainfrom
feat/release-plz-workflow

Conversation

@nichmor
Copy link
Copy Markdown
Owner

@nichmor nichmor commented Jan 14, 2026

Summary

  • Adds release-plz workflow to automate Rust releases
  • Removes old release.yml (tag-based releases replaced by release-plz)

What release-plz provides

  • Automatic CHANGELOG generation from conventional commits
  • Release PRs with version bumps in Cargo.toml
  • Automatic crates.io publishing when release PRs are merged
  • API breaking change detection via cargo-semver-checks

How it works

  1. On every push to main, release-plz analyzes commits since the last release
  2. It creates/updates a "release PR" with version bumps and changelog updates
  3. When you merge the release PR, it automatically publishes to crates.io and creates a GitHub release

Required setup

After merging, go to Settings > Actions > General > Workflow permissions and enable:

  • "Allow GitHub Actions to create and approve pull requests"

Test plan

  • CI passes
  • After merge, verify release-plz creates a release PR on next commit to main

🤖 Generated with Claude Code

- Add release-plz.yml workflow that creates release PRs and publishes to crates.io
- Remove old release.yml (tag-based releases replaced by release-plz)

Release-plz automates:
- CHANGELOG generation from conventional commits
- Version bumping based on commit types
- crates.io publishing when release PRs are merged

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant