-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathrelease-plz.toml
More file actions
59 lines (49 loc) · 2.2 KB
/
Copy pathrelease-plz.toml
File metadata and controls
59 lines (49 loc) · 2.2 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
# Based on the example provided in https://blog.orhun.dev/automated-rust-releases/
[workspace]
# path of the git-cliff configuration
changelog_config = "cliff.toml"
# enable changelog updates
changelog_update = true
# Do NOT run a free-form `cargo update` when generating the release PR.
# With this on, release-plz re-resolves the entire lockfile and picks the
# latest compatible version for every transitive dep, which can pull in
# crates whose MSRV exceeds our pinned toolchain (see rust-toolchain.toml
# and the `toolchain: 1.85.1` pins in ci.yml). This is the exact opposite
# of what we want. The assumption if we're making a release is that the
# current `master` is healthy, passing tests, and should be released verbatim.
# That means with all of the dependencies locked to the version they had when
# the last `master` build with all of its checked passed successfully.
dependencies_update = false
# Disable tags globally - only the main package will create a tag
git_tag_enable = false
# disable GitHub releases - cargo-dist handles this
git_release_enable = false
# labels for the release PR
pr_labels = ["release"]
# disallow updating repositories with uncommitted changes
allow_dirty = false
# disallow packaging with uncommitted changes
publish_allow_dirty = false
# Advance all of the packages' versions in sync, to avoid confusion
#
# Maintain a single changelog for all packages. Nearly all functionality will go in `cgx-core`, and yet no users will
# ever directly use `cgx-core`, they will use the CLIs that wrap it, so it doesn't make sense to treat these like they
# are separate for change logging purposes.
[[package]]
changelog_include = ["cgx-core", "cargo-cgx"]
changelog_path = "./CHANGELOG.md"
name = "cgx"
version_group = "cgx"
# Create a single tag for the version group instead of one tag per package
# This prevents cargo-dist from creating separate releases for each package
# See https://release-plz.dev/docs/extra/single-tag for more details
git_tag_enable = true
git_tag_name = "v{{version}}"
[[package]]
changelog_update = false
name = "cargo-cgx"
version_group = "cgx"
[[package]]
changelog_update = false
name = "cgx-core"
version_group = "cgx"