Skip to content

Commit

Permalink
chore: Only release-plz after release PRs (#1391)
Browse files Browse the repository at this point in the history
Stops releases from being created by new packages pushed to `main`.

https://release-plz.ieni.dev/docs/config#the-release_always-field

This saves us from having to temporarily configure `git_tag_enable` and
`git_release_enable` for each crate.
CQCL/tket2@73d6e65


Copied from CQCL/tket2#524
  • Loading branch information
aborgna-q authored Aug 2, 2024
1 parent b75dd09 commit fd609e0
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions release-plz.toml
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,13 @@ changelog_config = "cliff.toml"
git_tag_name = "{{ package }}-v{{ version }}"
git_release_name = "{{ package }}: v{{ version }}"

# Only create releases / push to crates.io after merging a release-please PR.
# This lets merge new crates to `main` without worrying about accidentally creating
# github releases.
#
# To trigger a release manually, merge a PR from a branch starting with `release-plz-`.
release_always = false

[[package]]
name = "hugr"
changelog_include = ["hugr-core", "hugr-passes"]
Expand Down

0 comments on commit fd609e0

Please sign in to comment.