Repository navigation
ci: install cargo-make --locked (every zip 2.x was yanked) - #204
Merged
Merged
Conversation
Every zip 2.x release on crates.io was yanked on 2026-10-16, and cargo-make 0.37.24 requires zip ^2, so an unlocked `cargo install cargo-make` fails to resolve. `--locked` builds from cargo-make's own Cargo.lock (zip 2.2.2), which still installs. Claude-Session: https://claude.ai/code/session_01SzES9BQh5PhrJhHdh9FSFw
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.
Every
zip2.x release on crates.io was yanked on 2026-10-16. cargo-make 0.37.24 (latest) requireszip = "^2", so an unlockedcargo install cargo-makenow fails with "failed to select a version for the requirementzip = \"^2\"".Fix: add
--lockedto the cargo-make install indeploy.yml,publish-freenet.ymlandintegration-test.yml(the last goes throughactions-rs/cargo, which runs the samecargo install).--lockedbuilds from cargo-make's own Cargo.lock (zip 2.2.2). I verified locally thatcargo install --locked cargo-makestill works.Without this, the next scheduled Freenet Deploy (daily, ~18:30 UTC) will fail at the cargo-make install step.
[AI-assisted - Claude]
https://claude.ai/code/session_01SzES9BQh5PhrJhHdh9FSFw