build(crypto/secp256k1): Update btcec/v2 to v2.3.4 (backport #3728)#3755
Merged
build(crypto/secp256k1): Update btcec/v2 to v2.3.4 (backport #3728)#3755
btcec/v2 to v2.3.4 (backport #3728)#3755Conversation
Running a `go get` should consistently build this project as per the README. However, the latest patch release of `btcec/v2` is not a proper Semantic Versioning patch. It removes an error return value from `ecdsa.SignCompact` function (btcsuite/btcd@e5d15fd). This is functionally a no-op, as the underlying function was hardcoded to always return `nil` as error. However, this is still a breaking change (compiler/build error) for all consumers of this function, as they historically expected two return values, but now only get one. Ref: btcsuite/btcd#2211 Ref: #3531 Ref: #3536 --- #### PR checklist - [ ] Tests written/updated - [x] Changelog entry added in `.changelog` (we use [unclog](https://github.com/informalsystems/unclog) to manage our changelog) - [ ] Updated relevant documentation (`docs/` or `spec/`) and code comments Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> (cherry picked from commit 17abb80) # Conflicts: # crypto/secp256k1/secp256k1.go
This comment was marked as resolved.
This comment was marked as resolved.
melekes
approved these changes
Aug 19, 2024
|
Would it be possible to backport these changes onto v0.37.x and v0.38.x? We use cometbft v0.37 but one of our new dependency imports automatically brings in btcec v2.3.4 which is incompatible. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Running a
go getshould consistently build this project as per the README. However, the latest patch release ofbtcec/v2is not a proper Semantic Versioning patch. It removes an error return value fromecdsa.SignCompactfunction (btcsuite/btcd@e5d15fd). This is functionally a no-op, as the underlying function was hardcoded to always returnnilas error. However, this is still a breaking change (compiler/build error) for all consumers of this function, as they historically expected two return values, but now only get one.Ref: btcsuite/btcd#2211
Ref: #3531
Ref: #3536
PR checklist
.changelog(we use unclog to manage our changelog)docs/orspec/) and code commentsThis is an automatic backport of pull request build(crypto/secp256k1): Update
btcec/v2to v2.3.4 #3728 done by Mergify.