Skip to content

signerproxy: Pin the log dependency to 0.4 - #772

Open
cdecker wants to merge 1 commit into
mainfrom
2026m11-signerproxy-log-pin
Open

cdecker wants to merge 1 commit into
mainfrom
2026m11-signerproxy-log-pin

Conversation

@cdecker

@cdecker cdecker commented Nov 19, 2026

Copy link
Copy Markdown
Collaborator

Summary

 # libs/gl-signerproxy/Cargo.toml
-log = "*"
+log = "0.4"

crates.io refuses wildcard requirements on upload, so gl-signerproxy 0.4.0 never published. 0.4 is the range Cargo.lock already resolves to (0.4.29), so the lockfile does not change.

Evidence

  • Before: the gl-signerproxy-v0.4.0 release run:
    error: failed to publish gl-signerproxy v0.4.0 to registry at https://crates.io
      the remote server responded with an error (status 400 Bad Request): wildcard (`*`) dependency constraints are not allowed on crates.io. Crate with this problem: `log`
    
    crates.io still has 0.3.0.
  • After: no wildcard requirement is left in a publishable crate (cargo metadata over the non-publish = false crates), and Cargo.lock is unchanged.

Merge Danger

Door: two-way

Blast Radius: gl-signerproxy

Releasing it afterwards takes either moving the gl-signerproxy-v0.4.0 tag, which points at d4a4146 and never published, onto the merge commit, or bumping to 0.4.1.

🤖 Generated with Claude Code

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

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant