chore: bump github.com/21-dot-dev/swift-secp256k1 from 0.17.0 to 0.23.2 in the swift group - #710
chore: bump github.com/21-dot-dev/swift-secp256k1 from 0.17.0 to 0.23.2 in the swift group#710dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the swift group with 1 update: [github.com/21-dot-dev/swift-secp256k1](https://github.com/21-DOT-DEV/swift-secp256k1). Updates `github.com/21-dot-dev/swift-secp256k1` from 0.17.0 to 0.23.2 - [Release notes](https://github.com/21-DOT-DEV/swift-secp256k1/releases) - [Changelog](https://github.com/21-DOT-DEV/swift-secp256k1/blob/main/CHANGELOG.md) - [Commits](21-DOT-DEV/swift-secp256k1@0.17.0...e70a10e) --- updated-dependencies: - dependency-name: github.com/21-dot-dev/swift-secp256k1 dependency-version: 0.23.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: swift ... Signed-off-by: dependabot[bot] <support@github.com>
|
PR author is in the excluded authors list. |
jvsena42
left a comment
There was a problem hiding this comment.
This does not build. Every build and test job on f91382e fails with Missing package product 'secp256k1' (exit 65) — the bump crosses 0.20.0, which renamed the module.
I verified the remediation against the upstream package: 0.23.2 exports only libsecp256k1, libsecp256k1_zkp, P256K and ZKP, no longer re-exports the C bindings, and P256K.KeyAgreement.PrivateKey / sharedSecretFromKeyAgreement(with:format:) both still exist, so no semantic change to the APIs Bitkit uses. It needs source changes dependabot cannot make.
Recommend closing this and bumping by hand. Since this is the crypto library behind recoverable-ECDSA backup auth and ECDH push decryption, re-run WatchOnlyAccountServiceTests and check a real push decrypt on device before shipping; Bitkit/Utilities/Keychain.swift also references secp and should be checked while you are in there.
| requirement = { | ||
| kind = exactVersion; | ||
| version = 0.17.0; | ||
| version = 0.23.2; |
There was a problem hiding this comment.
🟠 0.17.0 -> 0.23.2 crosses the 0.20.0 module rename; the app no longer builds
CI fails with Missing package product 'secp256k1' in Bitkit, BitkitTests and BitkitNotification. 0.20.0 renamed secp256k1 -> P256K and secp256k1_bindings -> libsecp256k1, and 0.23.2 no longer re-exports the C bindings. Needed alongside this bump: import P256K (+ P256K.KeyAgreement.*) in Crypto.swift and WatchOnlyAccountService.swift, import libsecp256k1 for the raw secp256k1_* calls in Crypto.swift, and the pbxproj product refs switched to P256K and libsecp256k1 for all three targets. Do this as a manual bump, not a dependabot merge, and re-run WatchOnlyAccountServiceTests plus a push-notification decrypt before shipping.
Bumps the swift group with 1 update: github.com/21-dot-dev/swift-secp256k1.
Updates
github.com/21-dot-dev/swift-secp256k1from 0.17.0 to 0.23.2Release notes
Sourced from github.com/21-dot-dev/swift-secp256k1's releases.
... (truncated)
Changelog
Sourced from github.com/21-dot-dev/swift-secp256k1's changelog.
... (truncated)
Commits
e70a10edocs: release version 0.23.2 with consolidated key-handling guide and termino...1914e20docs: consolidate key-handling articles into unified WorkingWithKeys guide (#...64d58b9build(deps): Bump github.com/21-dot-dev/swift-plugin-tuist from 4.195.3 to 4....81601dadocs: clarify terminology and tighten phrasing across DocC catalog (#1126)1a8955fbuild(deps): Bump github.com/21-dot-dev/swift-plugin-tuist from 4.195.2 to 4....0aa1d74build(deps): Bump github.com/21-dot-dev/swift-plugin-tuist from 4.195.1 to 4....7f0f85fbuild(deps): Bump github.com/csjones/lefthook-plugin from 2.1.6 to 2.1.8 (#1123)29634a6build(deps): Bump github.com/21-dot-dev/swift-plugin-tuist from 4.194.3 to 4....0cf4a80build(deps): Bump github.com/21-dot-dev/swift-plugin-tuist from 4.194.1 to 4....895983ebuild(deps): Bump github.com/21-dot-dev/swift-plugin-tuist from 4.193.4 to 4....Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions