Skip to content

Fix secp256k1 dependency - pin to exact version 0.17.0 #1 - #2

Open
hariria wants to merge 5 commits into
ALCOVE-LAB:mainfrom
hariria:main
Open

Fix secp256k1 dependency - pin to exact version 0.17.0 #1#2
hariria wants to merge 5 commits into
ALCOVE-LAB:mainfrom
hariria:main

Conversation

@hariria

@hariria hariria commented Oct 24, 2025

Copy link
Copy Markdown

The secp256k1.swift library changed product names between versions:

  • v0.17.0 uses 'secp256k1' product name
  • v0.18+ uses 'libsecp256k1' product name

This commit pins to v0.17.0 to match the API this SDK was built against.

Andrew Hariri and others added 5 commits October 23, 2025 17:17
The secp256k1.swift library changed product names between versions:
- v0.17.0 uses 'secp256k1' product name
- v0.18+ uses 'libsecp256k1' product name

This commit pins to v0.17.0 to match the API this SDK was built against.
Fix secp256k1 dependency - pin to exact version 0.17.0
Export Core, Types, Utils, and Transactions as separate library products
to allow consumers to import these modules independently. This fixes module
resolution issues when using the SDK from external packages.
Expose submodules as separate library products
@alex4506

Copy link
Copy Markdown

Hmm, seems there are some test erros @hariria

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.

2 participants