Skip to content

Conversation

tcharding
Copy link
Member

In preparation for release, bump the version, add a TODO placeholder as a changelog, and update the lock files.

@tcharding
Copy link
Member Author

I'm sitting in the airport; could not work out right now what has been changed that requires this so I put a TODO in the changelog, seems reasonable since it will be the same changelog for the non-beta release.

@apoelstra
Copy link
Member

All the musig structures are new in this version.

@apoelstra
Copy link
Member

@tcharding you need to re-run the vendoring script to increase the version of secp256k1-sys.

I think we should bump it to 0.12.0 rather than 0.12.0-beta.0 since we aren't expecting any API changes to -sys and our logic for separating symbol names in the C library doesn't handle suffixes.

@tcharding tcharding changed the title secp256k1-sys: Bump version to 0.12.0-beta.0 Release tracking PR: secp256k1-sys v0.12.0 Oct 10, 2025
In preparation for release, bump the version, add a changelog entry,
and update the lock files, and run the vendor script.
I ran the script and hit enter, enter, not really understanding what
it was asking.
@tcharding
Copy link
Member Author

Can you put me out of my misery and tell me exactly how to run the vendor script please? I've managed to just strip the numbers out of the symbols all together.

@apoelstra
Copy link
Member

@tcharding

cd secp256k1-sys
./vendor-libsecp.sh 0cdc758a56360bf58a851fe91085a327ec97685a

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