Bitcoin Core

This is a minor CI (Continuous Integration) configuration change. It adds a default value of 'scratch' to a Docker build argument to silence a harmless warning from Docker. There is no security issue here.

This commit only changes Bitcoin Core's internal continuous integration (CI) scripts. It adds a warning when the build cache (ccache) hit-rate is below 75% and sets a logging variable for macOS CI jobs. There is no change to the Bitcoin software that users run, no wallet or network code is touched, and no security vulnerability is present.

This commit only updates documentation in the CI (continuous integration) README file. It explains how to set up paid Cirrus Runners for faster automated testing and how forks can use free GitHub runners. There are no code changes and no security-relevant behavior changes.

This commit changes how Bitcoin Core's continuous integration (CI) build system decides how many parallel compilation jobs to run. Previously it hard-coded 10 jobs; now it detects the number of CPU cores on the machine. There is no security-relevant change here—it's purely a build-performance tuning adjustment.

This commit simply deletes an unused CI configuration file (.cirrus.yml) from the Bitcoin Core repository. It does not change any code that runs the Bitcoin network software, wallets, or consensus rules. There is no security issue here.

This commit adds a new automated linting job to Bitcoin Core's GitHub Actions CI workflow. Linting is a routine code-quality check that flags style issues and common mistakes; it does not change how the Bitcoin software itself runs or handle user funds, network traffic, or secrets.

This commit only adds a new MemorySanitizer (MSan) CI job to the GitHub Actions workflow file. It does not change any Bitcoin Core source code, runtime behavior, or network protocol. There is no security vulnerability here.

This commit adds a new continuous integration (CI) test job to Bitcoin Core's GitHub Actions workflow. It enables ThreadSanitizer (TSan) testing with the depends build system and disables the GUI. It also adds a system setting tweak (vm.mmap_rnd_bits=28) specifically for that TSan job to prevent crashes caused by high address space layout randomization (ASLR) entropy. This is a testing infrastructure change, not a change to Bitcoin Core's runtime code, consensus rules, wallet, networking, or any user-facing functionality.

This commit adds a new automated code-quality check called 'tidy' to Bitcoin Core's continuous integration (CI) pipeline. It does not change any Bitcoin software code, user-facing behavior, or network protocol. It only configures GitHub Actions to run an existing cleanup/linting script in a specific Ubuntu environment. There is no security vulnerability here.

This commit adds a new continuous integration (CI) test job for Bitcoin Core. It does not change any wallet, networking, consensus, or node code that end users run. It only tells the project's automated testing system to also run tests on CentOS with the GUI build. There is no security issue visible in this change.

This commit adds a new continuous integration (CI) test job to Bitcoin Core's GitHub Actions workflow. It does not change any production code, wallet logic, networking, or consensus rules. It simply tells the project's automated testing system to also run an existing test configuration ('previous releases, depends DEBUG') on GitHub-hosted runners in addition to wherever it ran before.

This commit adds a new continuous-integration (CI) job to Bitcoin Core's GitHub Actions workflow. It runs the project's fuzz tests with AddressSanitizer, UndefinedBehaviorSanitizer, and IntegerSanitizer enabled, using the existing native fuzzing environment. There is no code change to Bitcoin Core itself, no bug fix, and no security patch.

This commit adds a new continuous integration (CI) test job to Bitcoin Core's GitHub Actions workflow. It runs the existing test suite in a specific configuration: 32-bit i686 architecture, DEBUG build, and without inter-process communication (IPC). There is no code change to Bitcoin Core itself, only an addition to the CI configuration file.

This commit adds a new automated testing job to Bitcoin Core's GitHub Actions CI pipeline. It does not change any wallet, kernel, or consensus code, nor does it alter how the software behaves on users' machines. It simply tells the project's continuous integration system to run an existing test configuration ('No wallet, libbitcoinkernel') on every relevant build.

This commit adds a new GitHub Actions CI job that cross-compiles the Bitcoin Core graphical user interface for macOS without running tests. It is purely a build-pipeline configuration change and does not modify any production code, network behavior, or wallet logic.

This commit changes a Bitcoin Core continuous integration (CI) test script. It forces a re-install of Linux kernel headers when running an AddressSanitizer (ASan) test in a Docker container. The goal is to avoid CI failures when the host runner's Linux kernel is updated but a cached Docker image still contains older kernel headers. This is a build/test infrastructure fix, not a change to the Bitcoin software users run.

This commit is a routine internal change to Bitcoin Core's continuous integration (CI) setup. It removes a standalone GitHub Actions job for running sanitizers (ASan, LSan, UBSan) and merges that same job into a shared CI matrix. There is no change to the actual Bitcoin node software, wallet code, or network behavior, and nothing in the commit suggests a security fix or vulnerability.

This commit adds a new automated testing job for 32-bit ARM processors in Bitcoin Core's GitHub Actions CI workflow. It does not change any wallet, networking, consensus, or node code that end users run. It only affects internal continuous integration (CI) infrastructure.

This commit only changes a fuzz test file used for automated testing of Bitcoin Core's wallet fee logic. It adds a helper that simulates a higher minimum mempool fee during the test so the fuzzer can exercise more code paths. There is no change to production wallet or mempool code, and no security issue is present in the diff.

This is a harmless code cleanup in Bitcoin Core's test suite. A helper function used only by tests is being moved from one internal test file to another so it can be reused more easily. It does not change how the live Bitcoin network works and is not a security fix.

This commit is a small cleanup inside a fuzz test (automated randomized testing) for Bitcoin Core's wallet fee logic. It creates a dedicated test helper class so the fuzz harness can safely set and reset the fee estimator. There is no change to production code, no user-facing behavior change, and no security fix.

This commit only changes a fuzz test file. It introduces a fake/mock version of Bitcoin Core's fee estimator so the wallet fuzz test can control its outputs. There is no change to production code, no user-facing behavior change, and no security fix or vulnerability.

This commit is a routine update to Bitcoin Core's automated testing configuration for building Windows software from a Linux machine. It swaps the virtual machine image used by the CI job and replaces several inline setup steps with reusable internal actions. There is no change to the Bitcoin software itself, no user-facing change, and no security fix or vulnerability.

This commit is a routine cleanup of the project's GitHub Actions CI configuration. It introduces a small helper job that decides whether to use Cirrus-hosted runners or GitHub-hosted runners based on a repository name comparison. There is no security-relevant change; it only reorganizes existing logic to reduce repetition.

This commit adds a single environment variable to the project's GitHub Actions CI workflow. It tells Docker where to find a local Cirrus CI build cache server (127.0.0.1:12321). There is no security-relevant change: it does not introduce secrets, change permissions, modify network exposure, or alter how Bitcoin Core itself runs.