libsecp256k1

This is a tiny code cleanup in a benchmark program. It replaces a hardcoded number (16) with a named constant (ALIGNMENT) when calculating memory size. There is no security issue here.

This commit is a straightforward memory optimization for a cryptographic calculation routine. It reduces the amount of temporary memory used during batch elliptic-curve multiplications by storing intermediate values in smaller integer types. There is no indication of a security bug being fixed.

This commit only changes the version of the macOS virtual machine used by the project's automated testing system. It replaces an older, soon-to-be-retired macOS test image with a newer one. There is no change to the actual cryptographic code, no bug fix, and no security-relevant behavior change.

This commit simply removes a workaround in the continuous integration (CI) script that added a compiler flag for older versions of Valgrind. It does not change any cryptographic code, wallet logic, or network behavior, and has no direct security impact on the library itself.

This is a minor GitHub Actions CI cleanup. It removes a default shell command from a reusable workflow action and instead makes callers explicitly provide the command. There is no security-relevant change to the actual Bitcoin cryptography code or to how containers are built or executed.

This change is a routine cleanup of the project's automated testing configuration file. It replaces repeated copies of the same CI step with YAML anchors and aliases, which is purely a maintainability improvement. There is no change to the actual commands run, the software code, or any security-sensitive behavior.

This is a routine cleanup of the project's automated testing configuration. It renames and restructures how environment variables are grouped in GitHub Actions workflow files so the setup is more consistent across different test jobs. There is no change to the actual cryptographic code, no new capability for an attacker, and no security fix.

This commit is a routine cleanup of the project's automated testing configuration file. It replaces several copy-pasted 'Print logs' steps with a single reusable template reference, making the file shorter and easier to maintain. There is no change to the actual software code, no change to how tests run, and no security relevance.

This commit simply updates the version of a GitHub-provided action used to check out source code during automated testing. There is no indication of a security vulnerability or code change affecting the secp256k1 library itself.

This commit is a routine cleanup of the project's automated testing configuration file. It replaces many repeated copies of the same 'checkout the code' step with a single shared template reference. There is no change to the actual software code, no change to security settings, and no security relevance.

This change updates the project's automated testing setup. It adds a second compiler ('clang-snapshot', a preview version of the next Clang release) to the MemorySanitizer (MSan) CI job and installs an extra compiler support package needed by that snapshot compiler. There is no change to the cryptographic library code itself, no bug fix, and no security patch.

This is a build-system hygiene patch that suppresses a compiler warning in test-only sanitizer code. It does not change runtime behavior, fix a vulnerability, or affect how Bitcoin/crypto operations work. The change only tells Clang 21+ to ignore a new warning when using MemorySanitizer during tests.

This change only adjusts how a Docker container used for automated testing installs Debian packages. It sets an environment variable that tells Debian's package installer not to prompt for user input, which simply removes harmless warning messages during automated builds. There is no security issue here.

This commit simply updates a GitHub Actions helper used to build Docker containers from version 5 to version 6. It is a routine maintenance change to the project's continuous integration (CI) configuration and does not alter the cryptographic library code, build scripts, or any software that end users run.

This is a routine cleanup of the project's automated CI (Continuous Integration) configuration. It removes an unused 'tag' input from GitHub Actions Docker build steps and switches to referencing the most recently built Docker image by ID instead of by tag. There is no security issue here.

This commit changes how Bitcoin Core's libsecp256k1 project caches Docker images in its automated testing system. It adds a 'scope' label to GitHub Actions cache settings so that separate caches are kept for different CPU architectures (like x86_64 vs ARM). Previously, all architectures shared one cache, meaning only the most recently used image was kept. This is a CI infrastructure improvement, not a security fix.

This commit adds a new command-line option (-t or --target) to the project's internal test runner so developers can run a single test or a whole module instead of the entire test suite. It is a testing convenience feature with no apparent security relevance.

This commit adds a simple command-line option to the project's test runner that prints a list of all available tests and modules. It is a pure test-infrastructure convenience feature with no effect on the cryptographic library or any production code paths.

This commit adds a new optional '--log=1' command-line flag to the project's internal test runner so users can see when each test starts, finishes, and how long it took. It also adds a small safety check to make sure the test framework is initialized before tests are run. There is no change to cryptographic code, no network code, and no behavior that affects normal users of the library.

This commit adds a --help / -h command-line option to the project's internal test suite. It simply prints usage instructions and exits. There is no security-relevant change to any cryptographic code, network handling, or production library behavior.

This commit is purely a test-code refactoring. It reorganizes how the project's test cases are registered and run, allowing individual tests to be selected and run in parallel. No production cryptographic code is changed, and there is no indication this fixes or introduces a security vulnerability.

This commit is a pure test-infrastructure change. It introduces a small internal unit-test framework for the secp256k1 cryptographic library, replacing a long hand-written main() function with a registry of test cases and adding optional parallel test execution. It does not change any cryptographic code, public API, or production behavior, and it does not fix or introduce any security vulnerability.

This commit only changes documentation comments in a header file. It rewords descriptions of error and illegal-argument callbacks, fixes typos, and clarifies wording. No executable code, build system, or API behavior was changed, so it has no security impact on its own.

This commit only changes a documentation comment in a header file. It clarifies that if a user-supplied error callback returns instead of aborting, the API call's results are undefined and the callback may be triggered more than once. No code behavior was changed.

This commit fixes compiler warnings in build-system tests that detect whether x86_64 assembly can be used. It initializes a variable and adds a return statement to a small test program. These changes do not affect the actual cryptographic code, runtime behavior, or security of the library.