BTCPay Server

This commit only changes test configuration files for the BTCPay Server project. It adds the Bitcoin setting `unsafesqlitesync=1` to the docker-compose files used during automated testing. This setting makes test execution faster by relaxing how safely Bitcoin Core writes its SQLite wallet data to disk. It does not affect production BTCPay Server code or live deployments, and there is no indication it fixes or introduces a security vulnerability.

This commit fixes a typo in a package version number. The version string for the NBXplorer.Client package had an extra stray backtick character (`), which would break the build. Removing the backtick restores the intended version 5.0.6 and allows the project to compile normally. There is no security issue here.

This commit is a routine translation and localization update. It adds, removes, and updates user-visible text strings in BTCPay Server. There is no code logic change, no security fix, and no vulnerability introduced in the diff itself.

This commit simply updates a software dependency (NBXplorer.Client) from version 5.0.5 to 5.0.6. There is no information in the commit itself about what changed in the new version or whether it fixes any security issue. Based only on this diff, no security problem can be identified.

This commit updates several third-party software libraries and Docker base images to newer patch versions. It does not change BTCPay Server's own code. Such updates are routine maintenance and often include bug fixes or security fixes from upstream vendors, but the commit message gives no specific security reason and no vulnerability details are visible in the diff.

This commit is a routine version bump from 2.3.7 to 2.3.8. It only updates the version number and the changelog. There are no code changes that fix or introduce any security issue in this commit itself.

This commit updates several software libraries and changes how BTCPay Server reads Bitcoin wallet descriptors (the strings that define which addresses belong to a wallet). The title says it fixes a bug where Phoenixd lightning payments were wrongly marked as partial, but the actual code changes mostly replace an older output-descriptor parser with a simpler one and update documentation examples. The security relevance is unclear from the diff alone: it could be a routine bug fix, or the library updates could include security patches. There is no direct evidence in the commit of an exploit or a disclosed vulnerability.

This commit is a routine software-engineering change: it marks several internal service methods and fields as virtual or protected so that third-party plugins can extend them more easily. There is no security bug being fixed and no new vulnerability being introduced in the diff itself.

This commit fixes a bug where BTCPay Server's 'reserved addresses' list could show addresses from a previously replaced wallet. After a user swaps one wallet for another, the old reserved addresses are now filtered out by checking which addresses actually belong to the current wallet's derivation scheme in the NBXplorer database. The commit also adds a Playwright test that verifies old addresses disappear after wallet replacement and reappear if the original wallet is restored.

This commit adds two new read-only reports to the Subscriptions plugin in BTCPay Server: one listing subscribers and another showing credit history. It is a straightforward feature addition with no visible security changes, no permission changes, and no fixes to existing behavior. The included test simply verifies the reports load without crashing.

This commit only adds a new section to the project's Changelog.md file describing version 2.3.7. It lists new features and bug fixes but does not change any application code, configuration, or security settings. There is nothing in this commit that could directly affect security.

This commit only updates translation strings in a single C# file. It adds, removes, and reorders user-facing text labels (for example, new labels for subscription dates and recovery codes). There are no code logic changes, no security fixes, and no functional behavior changes visible in the diff.

This commit adds a simple optional comment field to the wallet send screen in BTCPay Server. Users can type a short note (up to 200 characters) when preparing a transaction, and that note is saved alongside the transaction after it is broadcast. There is no security issue visible in the change.

This commit fixes a timing issue in BTCPay Server's automated test suite. It ensures that when a test triggers a browser alert dialog, the test waits for the dialog to actually be accepted before continuing. Previously, the test could proceed before the dialog handler finished, causing unpredictable 'flaky' test failures. There is no change to production code or user-facing security behavior.

This commit fixes a potential race condition in how BTCPay Server updates the status of a Payment Request. Previously, the code read the record, changed its status in memory, and saved it back. If two processes did this at the same time, one update could overwrite the other, possibly causing duplicate or missed events. The fix uses a single SQL UPDATE statement that only changes the status if it is different, then checks the result before publishing an event. The commit message calls this a 'possible race condition' but does not describe a specific security outcome.

This commit adds an 'Update' button for disabled plugins in BTCPay Server's plugin management page. It lets users update a disabled plugin directly from the disabled-plugins list instead of scrolling to the available-plugins section. The change also fetches all plugins unfiltered once and does search filtering in memory, and adds unit tests. There is no clear security bug in the diff, but the change touches plugin installation commands and identifier matching, which are security-sensitive areas.

This commit only changes a test file. It replaces some direct text equality checks with Playwright's built-in 'expect element to contain text' helper, which waits for the text to appear rather than checking instantly. The goal is to make a flaky (sometimes failing) test more stable. There is no change to production code and no security relevance.

This commit is a small cleanup in the BTCPay Server subscriptions plugin. It removes redundant assignments to the PreviousPlan property (which is now set only through the constructor), makes a property read-only, fixes a test to wait for an event, and corrects a namespace reference. There is no indication this fixes a security vulnerability.

This commit makes two small fixes in the BTCPay Server Subscriptions plugin. It changes a test helper so two UI form-filling branches are mutually exclusive, and it tightens when a subscription plan change can be scheduled and updates statistics when a plan actually changes. There is no clear security vulnerability in the diff itself; it looks like a routine bug-fix or code-review follow-up.

This commit is a code reorganization: the existing Forms feature is moved from the core BTCPayServer project into its own plugin folder. Files are renamed and namespaces adjusted, but the actual form logic, validation, and behavior remain essentially unchanged. There is no indication this change fixes or introduces a security vulnerability.

This commit fixes a store dashboard widget that displays wallet balance charts and numbers. The changes ensure chart labels are rendered correctly (especially the last data point) and convert API timestamps from Unix seconds into ISO date strings that the chart library expects. There is no security-relevant change.

This commit updates the .NET runtime and SDK Docker images used to build and run BTCPay Server from version 10.0.200/10.0.4 to 10.0.201/10.0.5. These are patch-level updates to the underlying Microsoft .NET platform. Such updates typically include bug fixes and security fixes, but the commit message does not say this is a security update and no specific vulnerability is referenced. The change is routine maintenance rather than a fix for a known, actively exploited flaw in BTCPay Server itself.

This commit only changes a single version number in a build file from 2.3.6 to 2.3.7. There is no code change, no bug fix, and no security-related content in the diff.

This commit only updates the project's changelog file, adding one line describing a previously completed feature (wallet label filtering). It makes no code changes and has no security relevance.

This commit adds a search box to the wallet transaction label filter dropdown. When a wallet has more than 20 labels, users can now type to search instead of scrolling through a long list. It also shows how often each label is used and lists the 20 most popular labels first. There is no security-relevant change here.