BTCPay Server

This commit is a code reorganization: it moves the Crowdfund feature's files into a dedicated plugin folder and updates the controller to use newer ASP.NET Core patterns (primary constructor, area routing). It also makes a small change so that looking up a store for an app throws an exception if the store is missing, instead of returning null. There is no clear security fix or vulnerability being patched here.

This commit is purely a test-code refactor. It moves existing pull-payment and coin-selection tests into a new dedicated test file, removes duplicate copies from other test files, adds a couple of shared assertion helpers, and fixes compiler/style warnings. No production application code is changed, so it cannot affect the security of a running BTCPay Server instance.

This commit reorganizes automated browser tests by splitting some Playwright tests into a second CI job. It does not change any production code, user-facing behavior, or security-sensitive logic. The only non-test code change is a small tolerance adjustment in a refund amount assertion, which is still a test-only change.

This commit is a routine test modernization: it rewrites one existing automated UI test to use the Playwright testing framework instead of Selenium, and adds a single HTML data-testid attribute to the signed-out page header so the test can reliably locate it. There is no change to production logic, no security fix, and no vulnerability introduced.

This commit only changes the order of steps in an automated test script for the BTCPay Server project. It moves a 'Description Edit' step earlier in the test flow to try to fix a flaky (unreliable) test. There is no change to production code, no user-facing behavior change, and no security relevance.

This commit only changes a test file and adds a test marker to a UI message. It makes an automated browser test more reliable by waiting for elements to appear and checking their text in a more stable way. There is no security relevance.

This commit removes one blank line from a database migration file. It is a cosmetic formatting change with no functional or security effect.

This commit is a routine version bump from 2.3.2 to 2.3.3 for the BTCPay Server project. It updates the version number, adds a changelog entry describing new features and bug fixes, and adds a single debug log line to a test. The commit itself does not contain any application code changes that would fix or introduce a security vulnerability. The changelog mentions several bug fixes, but none are described by the vendor as security issues, and no independent security references are provided.

This commit is a routine version bump to 2.3.3 for the BTCPay Server project. It updates the version number, adds a changelog entry, and adds a single debug log line in a test file. The changelog describes several bug fixes and one notable change: CoinGecko rate sources are removed because CoinGecko now requires an API key. None of the changes in the diff itself are security fixes or introduce security-relevant code.

This commit only updates the default translation strings file in BTCPay Server. It adds, removes, and rewords user-facing text labels (for example, new labels for monetization features, language packs, and payment request labels). There are no code logic changes, no security fixes, and no changes to how the application behaves.

This commit fixes a bug where choosing certain cryptocurrency exchange rate sources would crash the BTCPay Server 'Stores/Rates' settings page. The root cause was that some rate source IDs contained characters like dashes or dots that are not valid in C# identifiers, which caused the rate-rule parser to throw an exception and crash the page. The fix adds validation when creating rate-source IDs, changes one provider's ID to remove a hyphen, sanitizes several IDs in a large exchange list, and makes the controller gracefully fall back when a preferred source cannot be found or parsed.

This commit adds new API features to BTCPay Server so users can create unsigned Bitcoin transactions (PSBTs) and broadcast already-signed transactions through the Greenfield API. It is a feature addition, not a bug fix. The code does not appear to introduce an obvious vulnerability, but it changes how wallet transactions are authorized and signed, which is security-sensitive. There is no vendor statement or external report saying this commit fixes a security issue.