Repository navigation
fix: temporarily skip semver checks for yanked zip baselines - #2958
Merged
Merged
Conversation
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.
Description
Temporarily disable release-plz's semver checks to unblock the Rust release PR update.
The failed release job successfully builds the current
rattler_index, but cannot resolve the published comparison baseline:rattler_index 0.33.4requiresrattler_package_streaming =0.27.14, which requireszip ^8. All zip 8 releases are yanked. #2957 updates main to zip 9, but cannot repair the published baseline.This changes only release-plz's API compatibility checks; it does not disable build/test CI or publish validation.
Release sequence:
rattler_package_streamingand the affected dependents, manually review API compatibility, and wait for CI before merging the release PR.semver_check = trueafter the zip 9 versions have been published and usable comparison baselines exist.How Has This Been Tested?
tomlliband asserted the only semantic change isworkspace.semver_checkfromtruetofalse.git diff --checkpassed.pixi run cargo-fmtpassed with no Rust changes.pixi run cargo-clippyattempted; blocked because the isolated worktree does not have the bundled libsolv submodule initialized (Bundled libsolv not found).AI Disclosure
Tools: ChatGPT via pi
User prompt (following investigation of the failed release job and the proposed temporary semver-check bypass):
Checklist: