Bump secp256k1

[athei]

This dep is out of date with substrate. Not sure why dependabot doesn't pick it up. Maybe because it is guarded behind an arch?

[jasl]

Could you made a release?
it blocks the upgrade to polkadot-v0.9.27

[jasl]

Or better backport to v3.x.x branch maybe?

[HCastano]

Ah shit, yeah I closed it without thinking much about it #1332 🙈

[HCastano]

Could you made a release? it blocks the upgrade to polkadot-v0.9.27

@jasl can you share what you're doing here and how/why it breaks?

[jasl]

Could you made a release? it blocks the upgrade to polkadot-v0.9.27

@jasl can you share what you're doing here and how/why it breaks?

error: failed to select a version for `secp256k1-sys`.
    ... required by package `secp256k1 v0.22.0`
    ... which satisfies dependency `secp256k1 = "^0.22.0"` of package `ink_env v3.1.0`
    ... which satisfies dependency `ink_env = "^3.1.0"` of package `pink-extension v0.1.13 (/Users/jasl/Workspaces/BlockChain/phala-blockchain/crates/pink/pink-extension)`
    ... which satisfies path dependency `pink-extension` of package `pink v0.1.0 (/Users/jasl/Workspaces/BlockChain/phala-blockchain/crates/pink)`
    ... which satisfies path dependency `pink` of package `phactory v0.0.1 (/Users/jasl/Workspaces/BlockChain/phala-blockchain/crates/phactory)`
    ... which satisfies path dependency `phactory` of package `replay v0.1.0 (/Users/jasl/Workspaces/BlockChain/phala-blockchain/standalone/replay)`
versions that meet the requirements `^0.5.0` are: 0.5.2, 0.5.1, 0.5.0

the package `secp256k1-sys` links to the native library `rustsecp256k1_v0_5_0`, but it conflicts with a previous package which links to `rustsecp256k1_v0_5_0` as well:
package `secp256k1-sys v0.6.0`
    ... which satisfies dependency `secp256k1-sys = "^0.6.0"` of package `secp256k1 v0.24.0`
    ... which satisfies dependency `secp256k1 = "^0.24.0"` of package `sp-core v6.0.0 (https://github.com/paritytech/substrate?branch=polkadot-v0.9.27#8eff668a)`
    ... which satisfies git dependency `sp-core` of package `beefy-primitives v4.0.0-dev (https://github.com/paritytech/substrate?branch=polkadot-v0.9.27#8eff668a)`
    ... which satisfies git dependency `beefy-primitives` of package `beefy-merkle-tree v4.0.0-dev (https://github.com/paritytech/substrate?branch=polkadot-v0.9.27#8eff668a)`
    ... which satisfies git dependency `beefy-merkle-tree` of package `substrate-test-runtime v2.0.0 (https://github.com/paritytech/substrate?branch=polkadot-v0.9.27#8eff668a)`
    ... which satisfies git dependency `substrate-test-runtime` of package `sc-service-test v2.0.0 (https://github.com/paritytech/substrate?branch=polkadot-v0.9.27#8eff668a)`
    ... which satisfies git dependency `sc-service-test` of package `phala-node v3.0.0 (/Users/jasl/Workspaces/BlockChain/phala-blockchain/standalone/node)`
Only one package in the dependency graph may specify the same links value. This helps ensure that only one copy of a native library is linked in the final binary. Try to adjust your dependencies so that only one package uses the links ='secp256k1-sys' value. For more information, see https://doc.rust-lang.org/cargo/reference/resolver.html#links.

[HCastano]

@jasl we have a new v3.3.1 release out for you

[jasl]

@jasl we have a new v3.3.1 release out for you

Thank you!