Repository navigation
release: develop into main - #19
Merged
Merged
Conversation
chore: merge main back into develop
release-plz only counts commits that touch files included in the package, so Cargo.toml now lists what a release is made of: src, the manifest, the lockfile and the license. readme = false keeps the README out (the archives copy it from the repo); a commit that only touches workflows, dev scripts, scanner configs, tests or docs opens no release PR and bumps no version. 0.1.2 was such a release. release-plz also runs git_only: a foreign crate named pgen exists on crates.io, and without it release-plz compared the manifest against that crate and produced a bump on every run, whatever the commits.
chore: release only on source changes
chore: merge main back into develop after v0.1.2
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.
developintomainMerge with a merge commit, not a squash. Merge preview shows no conflicts (
mainkeeps its 0.1.2 version line;developonly adds theincludelist andreadme = falseto Cargo.toml).What
developcarries sincev0.1.2includelist in Cargo.toml,git_onlyin release-plz.toml, so the foreignpgencrate on crates.io no longer drives version bumps)What happens after the merge
This is the last time a pipeline-only merge produces a release PR: the
includelist is itself a Cargo.toml change, which release-plz counts once. Expect the openchore(release): v0.1.3PR (#16, created by the old crates.io comparison right after v0.1.2) to be refreshed with an empty changelog. Leave it open: it is a proposal, not a release, and it will fill in when afeat:orfix:reachesmain.#17 (
mainback intodevelopafter v0.1.2) is still open and can be merged before or after this one; either order merges cleanly.