BTCPay Server

This commit removes an unused or redundant 'Id' property from a checkout view model in the Subscriptions plugin. The property was being set from a plan identifier but appears to have been 'confusing' rather than functional. There is no indication in the commit that this change fixes a security vulnerability.

This commit removes one configuration line ('auto_resolve_threads: true') from the project's CodeRabbit AI code-review settings file. It does not change any application code, payment logic, authentication, API behavior, or anything users interact with. There is no security relevance.

This commit corrects a spelling mistake in the project's changelog, changing 'upgradding' to 'upgrading'. It does not modify any program code, configuration, or documentation that affects how the software runs or behaves.

This commit changes how BTCPay Server handles crashes caused by plugins during startup. Previously, if a plugin caused a crash, the server would try to disable just that one plugin. The new code can disable all plugins when the server cannot tell which specific plugin is at fault, and it also avoids disabling built-in 'system' plugins. This is a reliability and recovery improvement rather than a fix for a remote attack.

This commit is a routine version bump from 2.3.0 to 2.3.1 for BTCPay Server, accompanied by a changelog entry. The changelog describes bug fixes for a startup crash loop caused by plugins, lost email settings after an update, and cleanup of monetized subscribers when users are deleted. There are no code changes in this commit that introduce or fix a security vulnerability directly; it is purely a release metadata update.

This commit is a small UI improvement: when you hover over a wallet transaction that came from a payment request, the tooltip now shows the payment request's human-readable title instead of its internal ID number. It also fetches all related payment requests in one database query rather than one by one. There is no security fix or vulnerability here.

This commit adds a single line to a test file, instructing an automated browser test to wait for an alert message before continuing. It is purely a test stability fix and does not change any production code, user-facing behavior, or security controls.

This commit only updates the project's Changelog.md file. It adds and tweaks changelog entries describing bug fixes made in other commits. No source code, configuration, or executable behavior was changed. There is no security relevance in the diff itself.

This is a tiny code cleanup in a background migration service. It removes an unnecessary check (`i.Title != null`) from a database query that selects old-style payment requests needing migration. There is no visible security relevance: the change does not alter access controls, validation, or data handling in a way that would create or fix a vulnerability.

This commit only adds two lines to the project's changelog file describing new features (payment request reports and improved filtering). It contains no code changes, no bug fixes, and no security-related content.

This commit is a routine UI rename and tidy-up. It changes the wallet label deletion page from saying 'Remove' to 'Delete', renames the underlying action method from RemoveWalletLabel to DeleteWalletLabel, and updates the matching URL from /remove to /delete. It also adds a breadcrumb navigation bar and fixes some indentation. There is no security-relevant change.

This commit adds a new feature that lets users rename labels attached to wallets and payment requests. It introduces new web forms, controller actions, and a database rename routine. The change is a feature addition, not a documented security fix. There is one notable design quirk: the wallet-label edit action does not show an explicit authorization attribute in the diff, while the payment-request edit action does. That could simply be because wallet routes already inherit authorization from the controller, but the diff alone does not prove it, so it should be treated as a low-confidence observation rather than a confirmed vulnerability.

This commit is a code cleanup/refactor touching three areas: payment-request search, wallet label lookup, and a label-manager icon URL. The most notable change is that the payment-request search no longer compares the user's search text directly against the database's Amount column as text; instead it tries to parse the search text as a decimal number and, if successful, compares it numerically. The wallet-label query is rewritten from LINQ to raw SQL. The JavaScript change fixes an icon path to use a configurable base URL and removes an explicit 'credentials: include' flag from a fetch call. None of these changes, on their own, look like a clear security fix, but the removal of the text-based amount comparison and the credentials flag are worth noting.

This commit is a performance refactor, not a security fix. It replaces many individual database lookups for payment-request labels with a single batched lookup, and makes a couple of minor cleanups (removing a comment, using a switch expression). There is no indication it changes any security boundary or fixes a vulnerability.

This commit is a routine test and UI cleanup. It reworks how old payment-request data is migrated into newer database columns, adds null checks so missing fields don't crash, and changes a table header from 'Reference Id' to 'Id'. There is no direct evidence of an exploitable security bug in the diff.

This commit fixes a database migration for payment requests in BTCPay Server. It changes how a new 'Title' column is populated from existing JSON data and adjusts the in-code migration logic. The changes appear to be a bug fix for a migration that previously did not run correctly, rather than a deliberate security patch. There is no clear evidence of an exploitable vulnerability in the diff itself.

This commit is a routine code cleanup of the wallet address label picker in BTCPay Server. It rewrites how the page caches and refreshes the list of available labels, removes an old Vue.js event listener, and adds a guard so the script does nothing if the expected HTML element is missing. There is no clear security bug being fixed and no security relevance is stated by the project.

This commit fixes a UI bug in BTCPay Server's wallet address list. Previously, when a user changed labels on a reserved Bitcoin address, the label filter on the page did not update to reflect the new labels, and an error in the label manager initialization could break the feature. The patch makes the address list listen for label-change events and refresh its internal label data so filtering works correctly after edits.

This commit adds new UI filters, a label system, and a reporting provider for payment requests. It also changes the search query to use a hand-written SQL statement. The change is described as a feature improvement, not a security fix. The SQL query uses Entity Framework's parameterized raw SQL, which generally protects against SQL injection, but the code mixes raw SQL with LINQ and introduces a new label-filtering path. There is no direct evidence in the commit of a vulnerability being fixed or introduced, but the raw SQL and label-filtering logic are worth reviewing carefully because mistakes in those areas can lead to security bugs.

This commit updates test-only Docker configuration files. It upgrades the PostgreSQL database image used in automated testing from version 13.13 to 18.1, fixes indentation, and adds a persistent data volume for the test database. These files are part of the project's internal test harness and are not used in production deployments. There is no direct security fix or vulnerability being patched here.

This commit updates the PostgreSQL database version used only in BTCPay Server's automated test environment from version 13.23 to 18.1. It also changes the data directory mount path inside the container. There is no indication this affects production systems or fixes a security vulnerability.

This commit updates the PostgreSQL database version used only in BTCPay Server's automated test environment from 13.13 to 13.23, and adds a persistent data volume for that test database. It does not change production code. The newer PostgreSQL patch release likely fixes bugs and security issues in the database software itself, but the commit does not address any vulnerability in BTCPay Server's own code.

This commit adds a simple shell script used by BTCPay Server maintainers to automate creating and pushing a Git version tag when publishing Docker images. It does not change application code, user-facing behavior, or any security-sensitive logic. There is nothing in the commit that introduces a vulnerability or fixes one.

This commit is a routine code refactor that lets webhook event providers run their lookup logic asynchronously. It changes a synchronous method to an async one and updates callers to await it. There is no security issue visible in the diff.

This commit fixes a flaky automated test for BTCPay Server's subscription/monetization feature. The code change removes a guard that previously prevented a subscriber's plan from being restarted if it had already started. The test change waits for a background activation event and reloads the page before checking the UI. On its own, the patch looks like a timing/test-stability fix rather than a clear security fix, but removing the 'already started' guard could, in theory, allow duplicate plan activations or repeated credits if the event handler runs more than once.