BTCPay Server

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 adds a new feature to BTCPay Server's subscription plugin that lets users schedule a plan upgrade or downgrade to take effect at the end of their current billing period, instead of happening immediately. It also lets users cancel a scheduled change. The change is a normal feature addition and does not appear to fix or introduce a security vulnerability based on the code shown.

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 fixes a privilege escalation bug in BTCPay Server's Greenfield API. Two authorization checks were passing 'null' instead of the actual store ID when verifying whether a user could auto-approve pull payments or payouts. In BTCPay Server's authorization system, a null resource likely causes the check to fall back to a global permission evaluation, meaning a user who only had permission on one store could potentially approve or auto-approve pull payments/payouts for other stores where they should have been denied. The patch simply passes the correct storeId so the permission is scoped properly.

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.