BTCPay Server

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 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 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 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 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 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.