chore(release): v0.3.1 - #45
Merged
Merged
Conversation
Version the Windows-installer repair and the wider architecture matrix. release-plz did not open its usual release PR for this bump: it ignores packages with `publish = false` in Cargo.toml, which 210143b added after v0.3.0, so its release-pr command has been returning {"prs":[]} ever since. Bumping by hand keeps the release moving; the release-plz regression is tracked separately.
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
1 participant
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.
Bumps
Cargo.toml/Cargo.lockto 0.3.1 and adds the CHANGELOG entry, so the tagv0.3.1satisfies theplanjob's version guard inrelease.yml.Releases the Windows-installer repair from #44 and the wider architecture matrix.
Why this is a hand-rolled bump
release-plznormally opens this PR. It stopped:release-plzignores packages withpublish = falsein Cargo.toml, which 210143b added after v0.3.0 (intending "version from git tags"). Since then itsrelease-prcommand returns{"prs":[]}andreleasesaysnothing to release— silently, with a green run. No release PR has been opened since v0.3.0.That regression is not fixed here; it needs a separate change (most likely moving the
publish = falseintent entirely intorelease-plz.toml, which already carries it, and verifying against the release-plz docs rather than guessing).What merging this unblocks
Pushing the
v0.3.1tag afterwards runsrelease.ymlfor the first time with the new pipeline, which exercises what could not be tested from a PR:<digest> <asset>sidecar on all three runner OSesverify-assetsgateaarch64-pc-windows-msvc(Windows ARM64) leg, never yet compileddit updateon Windows, which stays broken for anyone on v0.3.0 until a release ships the fixed parserNeed help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.