Upcoming changes constitute breaking public API changes to the secp256k1 module, therefore, this follows the process for introducing major API breaks which consists of: - Bump the major version in the go.mod of the affected module if not already done since the last release tag - Add a replacement to the go.mod in the main module if not already done since the last release tag - Update all imports in the repo to use the new major version as necessary - Make necessary modifications to allow all other modules to use the new version in the same commit - Repeat the process for any other modules the require a new major as a result of consuming the new major(s) |
||
|---|---|---|
| .. | ||
| doc.go | ||
| go.mod | ||
| go.sum | ||
| mining.go | ||
| policy_test.go | ||
| policy.go | ||
| README.md | ||