chore: release v0.8.11 - #1643
Merged
Merged
Conversation
|
Merged
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.
Finish the interrupted v0.8.11 release. #1637 merged as
bd5c1e76, but rustc 1.99.0 landed the same day and therelease-plz releasestep died atcargo publish's tarball verify (RUSTFLAGS=-D warnings) after publishing five of the thirteen crates:openlogi-assets,openlogi-device-registry,openlogi-camera,openlogi-core,openlogi-hidpp-deriveare on crates.io at 0.8.11; the other eight and thev0.8.11tag are not. #1638 fixed the lints on master, but the release job only runs for achore: releasehead commit and would check outbd5c1e76again on a dispatch, so it needs a new release commit whose tree carries the fix.This is the same recovery shape as #874 for v0.7.10, minus the version bump: nothing in the published half is wrong, so 0.8.11 is completed rather than skipped.
git-cliffis not installed locally, so the section is written by hand from.config/cliff.toml).chore: release v0.8.11 (#<this PR>).cargo xtask release checkout-version-bumppicks the newest commit with that subject, so the release job runs on this merge commit, release-plz skips the five crates already on the registry (already published), publishes the remaining eight, and cutsv0.8.11here;release.ymlthen builds the installers.Testing
cargo xtask release check-publishon master064c520a(same tree plus this changelog): publish closure valid, 14 publishable packages.release_plz_core::command::release(pkg_is_published→already published, continue).