Skip to content

chore(deps): update rust crate secp256k1 to 0.30 - autoclosed#233

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/secp256k1-0.x
Closed

chore(deps): update rust crate secp256k1 to 0.30 - autoclosed#233
renovate[bot] wants to merge 1 commit intomainfrom
renovate/secp256k1-0.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 20, 2024

This PR contains the following updates:

Package Type Update Change
secp256k1 workspace.dependencies minor 0.29 -> 0.30

Release Notes

rust-bitcoin/rust-secp256k1 (secp256k1)

v0.30.0

  • Allow signing variable-length messages #​706
  • Bump MSRV to 1.63 #​709
  • Deprecate Message::from_digest_slice in favor of Message::from_digest #​712
  • Truncate debug output of SecretKey; tighten bitcoin_hashes dependency version #​722
  • Simplify and improve consistency of secret key types' debug output #​726
  • Simplify and improve consistency of public key types' debug output #​745
  • Feature-gate KeyPair::from_str on global-context or alloc #​728
  • Add infallible constructors for schnorr::Signature from byteslices #​730
  • Deprecate slice-parsing methods in favor of array-parsing ones #​737
  • Make RecoveryId an enum rather than integer #​743

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Dec 20, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --workspace
    Updating crates.io index
error: failed to select a version for `secp256k1`.
    ... required by package `teepot v0.3.0 (/tmp/renovate/repos/github/matter-labs/teepot/crates/teepot)`
versions that meet the requirements `^0.30` are: 0.30.0

the package `teepot` depends on `secp256k1`, with features: `rand-std` but `secp256k1` does not have these features.


failed to select a version for `secp256k1` which could resolve this conflict

@renovate renovate bot requested a review from a team as a code owner December 20, 2024 12:01
@renovate renovate bot force-pushed the renovate/secp256k1-0.x branch 2 times, most recently from 8f5afc1 to c92eb4e Compare December 20, 2024 16:13
@renovate renovate bot force-pushed the renovate/secp256k1-0.x branch 3 times, most recently from 97af48f to b740619 Compare January 13, 2025 14:31
@renovate renovate bot force-pushed the renovate/secp256k1-0.x branch 3 times, most recently from 0e679df to 7441089 Compare January 17, 2025 12:19
@renovate renovate bot force-pushed the renovate/secp256k1-0.x branch 7 times, most recently from b5aa9fc to 99f9562 Compare February 10, 2025 13:51
@renovate renovate bot force-pushed the renovate/secp256k1-0.x branch from 99f9562 to 444db8d Compare February 10, 2025 14:40
@renovate renovate bot changed the title chore(deps): update rust crate secp256k1 to 0.30 chore(deps): update rust crate secp256k1 to 0.30 - autoclosed Feb 10, 2025
@renovate renovate bot closed this Feb 10, 2025
@renovate renovate bot deleted the renovate/secp256k1-0.x branch February 10, 2025 19:00
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.

0 participants