BTCPay Server

This commit reverts a planned removal of LNDHub support by updating a single Lightning library version and editing the changelog. It is a feature restoration, not a security fix. There is no evidence in the commit of any vulnerability, exploit, or security-relevant change.

This commit fixes a flaky automated test for the global search feature. The JavaScript change makes the search run automatically if a query is already present when the search UI opens, and the test code is simplified to remove a special screenshot-on-failure workaround. There is no security issue here.

This commit is a routine maintenance update for BTCPay Server. It removes support for three older/deprecated Lightning payment backends (Lightning Charge, LNDHub, and LNBank), updates the phoenixd integration, bumps a couple of library versions, and adjusts tests accordingly. There is no indication in the commit that this fixes an active security vulnerability or introduces new attack paths.

This commit fixes a performance problem on the BTCPay Server 'Policies' settings page. Previously, the page tried to load a dropdown list of every app on the server, which could time out or crash when there were many apps. The fix replaces the dropdown with a simple text box where the administrator types an app ID directly. It also adds validation to reject invalid app IDs instead of crashing. The change is primarily a reliability/performance fix, but it slightly changes how app IDs are entered and validated.

This commit simply adds missing translated text labels for a global search feature. It changes hardcoded English hint text into references to the project's translation system so the hints can appear in other languages. There is no security relevance.

This commit changes a single user-visible label from a plain English string to a translatable string. It is a routine localization fix with no security relevance.

This commit only adds one line to the project's changelog, documenting that a bug where Lightning invoices were silently dropped on reconnection has been fixed. The actual code change happened elsewhere, so this commit itself does not modify any program logic or fix any vulnerability directly.

This commit only adds new text strings for a 'bulk archive pull payments' feature and records it in the changelog. There is no code logic change, no security fix, and no behavior that could be exploited. It is a routine localization/changelog update.

This commit adds a single new translation string to the application's default translation file. It is a localization-only change with no security relevance.

This commit removes database-provider checks from two old database migration files and adds developer instructions for creating future migrations. It does not change application behavior for users, fix a vulnerability, or introduce new functionality. The SQL inside the migrations is unchanged; it now simply runs unconditionally rather than only when PostgreSQL is detected.

This commit only adds a single line to the project's changelog, documenting that a missing 'Uninstall' button for language packs was fixed. It changes no program code, configuration, or executable files, so it cannot by itself introduce or fix any security issue.

This commit adds a new third-party plugin called 'cashu-plugin' to BTCPay Server's automated compatibility-check script. The script clones the plugin's repository, initializes its submodule, wires it against the current BTCPay Server code, and builds it in CI. There is no code change to BTCPay Server itself, no bug fix, and no security-related content in the commit message or diff.

This commit simplifies a CircleCI script that checks whether third-party BTCPay plugins still compile against the current BTCPay Server code. It removes a comparison against an older baseline version and instead just builds plugins against the checked-out code. There is no indication this change affects the security of the BTCPay Server software itself or its users.

This commit only changes the project's CI/CD configuration file on CircleCI. It adds a missing 'plugin_compatibility' job definition and includes that job in the release workflow. There is no change to application code, no bug fix in the software users run, and no security-related content in the commit message or diff.

This commit only changes a test helper file used in automated UI testing. It replaces a manual sequence of keyboard shortcuts with calls to existing helper methods that do the same thing, in order to make a flaky test more reliable. There is no change to production code and no security relevance.

This commit only adds a single line to the project's changelog describing a prior user-interface bug fix: a date-picker dropdown in the invoice filter showed white text on a white background when Dark Mode was enabled. There is no code change, no security fix, and no functional behavior change in this commit.

This commit updates the .NET runtime and SDK versions used to build and run BTCPay Server. It is a routine dependency bump, likely to pick up bug fixes and security patches released by Microsoft. The commit itself does not describe any specific vulnerability or attack, but running older .NET versions can expose software to known security flaws.

This commit updates several third-party software libraries (dependencies) used by BTCPay Server to newer patch versions. It also adds a few new user-interface translation strings and records a bug fix in the changelog. The dependency bumps are routine maintenance that may include undisclosed security fixes from upstream vendors, but the commit itself does not describe any specific vulnerability or attack.

This commit only updates the project's changelog file, adding one line describing a UI fix for an invoice date filter widget. There is no code change and no security relevance in the diff itself.

This commit only updates the project's changelog file, adding a single line describing a user-interface improvement (inline QR code and copy button for a Store ID). There is no code change, no security fix, and no functional change to the software.

This commit only updates translation strings in a single C# resource file. It adds, removes, and rewords user-facing text labels (for example, changing '2FA' wording to 'Authenticator', adding labels for new passkey and multisig wallet features, and removing unused strings). There are no code logic changes, no security fixes, and no behavior changes.

This commit adds a single line to a test file to wait for the web page to finish loading before checking its content. It is a test reliability fix, not a security fix, and does not change any production code.

This is a one-line change in a test file that updates the name of a database migration being tested. It fixes a broken build caused by a renamed migration and has no security relevance.

This commit adds a new multisignature wallet setup feature to BTCPay Server. It introduces new database tables, UI flows, controllers, services, and tests for creating and managing multisig wallets. The changes are a feature implementation, not a security fix or vulnerability patch. There is no indication in the commit or supplied references that this addresses a security issue.

This commit swaps a regular dictionary for a thread-safe concurrent dictionary when caching store data attached to a web request. The stated goal is to prevent rare, random server crashes caused by multiple threads accessing the cache at the same time. It is a hardening fix rather than a clear-cut exploitable vulnerability, and the commit message does not frame it as a security issue.