Repository navigation
Conversation
crates.io rejected gl-signerproxy 0.4.0 with "wildcard (`*`) dependency constraints are not allowed on crates.io", for `log = "*"`. 0.4 is the version range Cargo.lock already resolves to (0.4.29).
This branch has not been deployed
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.
Summary
crates.io refuses wildcard requirements on upload, so gl-signerproxy 0.4.0 never published.
0.4is the rangeCargo.lockalready resolves to (0.4.29), so the lockfile does not change.Evidence
gl-signerproxy-v0.4.0release run:cargo metadataover the non-publish = falsecrates), andCargo.lockis unchanged.Merge Danger
Door: two-way
Blast Radius: gl-signerproxy
Releasing it afterwards takes either moving the
gl-signerproxy-v0.4.0tag, which points at d4a4146 and never published, onto the merge commit, or bumping to 0.4.1.🤖 Generated with Claude Code