Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add release-plz #2

Merged
merged 1 commit into from
Nov 15, 2024
Merged

Add release-plz #2

merged 1 commit into from
Nov 15, 2024

Conversation

berkus
Copy link
Contributor

@berkus berkus commented Nov 15, 2024

Automatic release/publish pipeline.

You'll need to do two things to set it up: one mandatory and one optional.

Mandatory step:

  1. generate a publish token on crates.io (preferably scoped to avra-rs, needs only "publish new packages" permission)
  2. Paste it into an env var called CARGO_REGISTRY_TOKEN in github:
image

Optional step:

  1. Add branch protection on the master branch, forbid direct commits.

If you don't - release-plz will trigger a release immediately after a merge to master and will commit a new release into master directly.
With protection, release-plz will create a PR with all the changes it wants to do and only after this PR is merged it will make a tag and a release, so this lets review changes before releasing.

(First release might need to be patched manually a bit to synchronize changelog to what release-plz expects.)

@no111u3 no111u3 merged commit c6a4054 into no111u3:master Nov 15, 2024
@berkus berkus deleted the feat/add-release-plz branch November 15, 2024 14:01
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.

2 participants