What changed, and why it matters
This commit is purely a release bookkeeping change. It renames the 'Unreleased' section in the changelog to version 0.7.1, adds an ABI compatibility note, and flips a build flag from 'not a release' to 'is a release'. No code behavior changes and no security fix is introduced here.
No security action needed; treat as routine release preparation.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff only touches CHANGELOG.md and configure.ac. It finalizes the 0.7.1 release metadata: updates the changelog header, adds an ‘ABI backward compatible with 0.7.0’ note, updates the GitHub compare link, and sets _PKG_VERSION_IS_RELEASE from false to true. There are no source, test, or build-logic modifications that affect runtime behavior.
Changed components
Inspect captured patch +6 / −3
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 92ad923..29d23a9 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -5,7 +5,7 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-## [Unreleased]
+## [0.7.1] - 2026-01-26
#### Changed
- Tests: Introduced a unit test framework with support for parallel test execution, selective test running, and named command-line arguments. Run `./tests -help` for usage information.
@@ -14,6 +14,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Increased the number of cases where the library attempts to clear secrets from the stack.
- build: Fixed x86_64 assembly feature check that could fail when user-provided `CFLAGS` included `-Werror`. This would cause the build to fall back to the slower C implementation instead of using the optimized x86_64 assembly.
+#### ABI Compatibility
+The ABI is backward compatible with version 0.7.0.
+
## [0.7.0] - 2025-07-21
#### Added
@@ -194,7 +197,7 @@ This version was in fact never released.
The number was given by the build system since the introduction of autotools in Jan 2014 (ea0fe5a5bf0c04f9cc955b2966b614f5f378c6f6).
Therefore, this version number does not uniquely identify a set of source files.
-[unreleased]: https://github.com/bitcoin-core/secp256k1/compare/v0.7.0...HEAD
+[0.7.1]: https://github.com/bitcoin-core/secp256k1/compare/v0.7.0...v0.7.1
[0.7.0]: https://github.com/bitcoin-core/secp256k1/compare/v0.6.0...v0.7.0
[0.6.0]: https://github.com/bitcoin-core/secp256k1/compare/v0.5.1...v0.6.0
[0.5.1]: https://github.com/bitcoin-core/secp256k1/compare/v0.5.0...v0.5.1
diff --git a/configure.ac b/configure.ac
index 6028ee2..97ea225 100644
--- a/configure.ac
+++ b/configure.ac
@@ -6,7 +6,7 @@ AC_PREREQ([2.60])
define(_PKG_VERSION_MAJOR, 0)
define(_PKG_VERSION_MINOR, 7)
define(_PKG_VERSION_PATCH, 1)
-define(_PKG_VERSION_IS_RELEASE, false)
+define(_PKG_VERSION_IS_RELEASE, true)
# The library version is based on libtool versioning of the ABI. The set of
# rules for updating the version can be found here:
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.