Bitcoin Core

This commit simply undoes a previous user-interface tweak for Linux Wayland users. The original workaround tried to force a Bitcoin Core window to the front by temporarily making it stay-on-top. Removing it restores the older, simpler window-raising behavior. There is no security issue visible in this change.

This change only adds an installation instruction file to Linux release packages. It does not modify any executable code, network behavior, or security-sensitive logic.

This commit simply adds one line to Bitcoin Core's automated CI (continuous integration) workflow so that the GUI unit tests for the Windows build are executed alongside existing tests. It is a testing infrastructure change, not a code change to the Bitcoin software itself, and has no direct security relevance.

This commit is a routine cleanup of Bitcoin Core's continuous integration (CI) scripts. It removes an old option that let CI jobs use BusyBox utilities instead of GNU tools, because a dedicated Alpine Linux CI job now covers BusyBox testing. It also removes a now-unused temporary directory for executables and enables stricter shell error handling in one script. There is no user-facing change, no change to the Bitcoin node software, and no security relevance.

This commit only shortens the display name of one automated testing job in the project's GitHub Actions configuration. It removes the words 'no depends' from a CI job label. There is no code change, no security fix, and no functional impact on the Bitcoin Core software or its users.

This commit only changes code-formatting rules and reorders one test file's #include lines accordingly. It has no effect on program behavior or security.

This commit is a minor documentation cleanup in Bitcoin Core's CI (continuous integration) README. It removes an unnecessary 'bash -c' wrapper from example shell commands, showing users they can pass environment variables directly to 'env' instead. There is no security-relevant change to the software itself.

This commit simply changes where Bitcoin Core's build system downloads some Qt source files from one official Qt location (code.qt.io) to another official mirror (GitHub's raw content server). The downloaded files are still verified by fixed SHA-256 hashes, so even if the new host were malicious, the build would reject tampered files. There is no security vulnerability here.

This commit fixes a minor developer-facing bug in how Bitcoin Core parses text-based wallet descriptors. A recent code change had made the parser accept raw character spans, which accidentally included the hidden null terminator at the end of C++ string literals. That caused the parser to reject valid descriptors with a misleading 'Invalid characters in payload' error. The fix switches the public API to use std::string_view, which does not include the trailing null byte, and adds a regression test. It is not a consensus or network security issue.

This commit updates the expat XML parsing library used by Bitcoin Core's build system from version 2.4.8 to 2.7.3. Expat is a widely-used library for processing XML data, and newer versions often fix security bugs found in older releases. The change also removes an old build patch and a workaround that were only needed for the older expat version. However, the commit message itself does not say this is a security fix, and no specific vulnerability is mentioned.

This is a test-only helper script that downloads old Bitcoin Core release binaries for testing. The change simply retries a failed download once after a 12-second wait. It is not a security fix and does not affect the Bitcoin Core software users run.

This commit updates the libxcb library used in Bitcoin Core's build dependencies from version 1.15 to 1.17.0. It also removes an obsolete build option and adjusts a patch that removes an unneeded pthread-stubs dependency so it also covers more operating systems. This is a routine dependency maintenance change, not a fix for a known Bitcoin Core security bug.

This commit updates a build dependency called xcb_proto from version 1.15.2 to 1.17.0 inside Bitcoin Core's dependency system. It only changes a version number, download URL extension, and the cryptographic hash used to verify the downloaded file. There is no direct evidence in the commit that this fixes a security vulnerability, but updating dependencies can sometimes include upstream security fixes.

This commit only changes code formatting rules. It tells the project's automated style tool (clang-format) to place constructor initializer list items on separate lines instead of packing them together. The only code change is a reformatting of one constructor in net.cpp to match the new style. There is no functional change to the Bitcoin software and no security impact.

This commit updates a build dependency called libxcb-util-wm from version 0.4.1 to 0.4.2 inside Bitcoin Core's 'depends' packaging system. It only changes the version number and the expected file hash (SHA-256) used to verify the downloaded source. There is no statement in the commit or supplied references saying this fixes a security problem, and no details about what changed in libxcb-util-wm 0.4.2 are provided. On its own, this looks like a routine dependency refresh rather than a confirmed security patch.

This commit simply updates a third-party graphics library used by Bitcoin Core's build system from version 0.1.5 to 0.1.6, along with its corresponding checksum. There is no indication in the commit itself that this fixes a security problem, and no security-relevant information is provided.

This commit updates the libxcb dependency used when building Bitcoin Core from source. It bumps the version from 1.14 to 1.15, switches the download archive format from .tar.xz to .tar.gz, updates the SHA-256 checksum, and refreshes a documentation link. There is no direct evidence in the commit that this fixes a specific security vulnerability, but dependency updates can include upstream security fixes.

This commit simply updates a dependency package version for libxcb-util-image from 0.4.0 to 0.4.1 in Bitcoin Core's build system, along with its corresponding SHA-256 hash. There is no indication in the commit itself of any security issue. It is a routine dependency bump.

This commit updates a build dependency, libxcb-util, from version 0.4.0 to 0.4.1 in Bitcoin Core's packaging system. It only changes the version number and the expected file hash (SHA-256) used to verify the downloaded source. There is no direct evidence in the commit that this fixes a security vulnerability, but dependency updates can sometimes include upstream bug or security fixes. Without external references, the security relevance is unclear.

This commit simply bumps the version of a third-party graphics-related library (libxcb-util-renderutil) used when building Bitcoin Core's dependencies. The change updates the version number and its corresponding cryptographic hash so the build system downloads the newer release. There is no direct evidence in the commit that this fixes a security vulnerability, and the library is only used in build tooling for graphical wallet support, not in Bitcoin's core networking or consensus code.

This commit updates a dependency used by Bitcoin Core's build system from version 0.4.0 to 0.4.1 of libxcb-util-keysyms, a small helper library for X11 keyboard handling. The change itself is a routine version bump with a new checksum. There is no direct evidence in the commit that this fixes a security vulnerability, but updating dependencies can sometimes address bugs or security issues in the upstream library.

This commit simply bumps the version of a third-party graphics-related library (libXau) used in Bitcoin Core's build dependencies from 1.0.9 to 1.0.12, updating the corresponding download hash. There is no indication in the commit itself that this fixes a security issue, and no security references were provided.

This is a code cleanup (refactor) that changes how one internal data structure receives a known-valid block index. It replaces a raw pointer with a C++ reference because the value is never null. There is no functional change to how Bitcoin validates blocks, syncs headers, or handles network data, and no security vulnerability is fixed or introduced.

This commit fixes a test-only race condition in a Bitcoin Core functional test. It changes which node is checked first when verifying that a newly submitted block has propagated, so the test waits for the local node to update its own chain before checking that all nodes agree. There is no change to production code, no user-facing behavior change, and no security vulnerability in the Bitcoin Core software itself.

This commit is a one-word documentation cleanup. It removes the phrase '(default: none)' from the help text describing the -i2psam command-line option in Bitcoin Core. The actual behavior of the software does not change; only the user-visible description is slightly simplified for consistency with other options.