BTCPay Server

This commit fixes a YAML syntax error in two test docker-compose files. Trailing commas after environment variable values were removed in one file, and a missing environment variable was added in the other. This is purely a build/test configuration fix with no security relevance.

This commit only changes test code. It fixes a flaky automated UI test by replacing two generic page-load waits with a helper that waits for a specific logged-in URL, and corrects the logic for deciding whether Playwright browser tests run in headless mode. There is no change to production code and no security relevance.

This is a one-line change in a test file that fixes a C# compiler/build error by switching from object-initializer syntax to a named parameter. It has no effect on the actual BTCPay Server application or its security.

This commit removes a single line of code that treated the 'comment' field as a special verbose metadata field in invoice reports. The change appears to be a cleanup: the comment field is already exported separately as 'InvoiceComment', so this branch was redundant. There is no indication this affects security.

This commit adds a new editable comment field to BTCPay Server invoices. Store staff can add private notes to invoices through the web interface or API, and these comments appear in invoice reports. The change is a normal feature addition, not a security fix. There is no indication in the commit that it addresses any vulnerability or security incident.

This commit simply updates a single software library dependency from version 1.7.3 to 1.7.4. There is no information in the commit itself about what changed in that library or whether it fixes any security issue. Without knowing the contents of the library update, no security conclusion can be drawn from this diff alone.

This commit is a routine UI/UX refactor of the BTCPay Server reports page. It replaces a custom date-picker and JavaScript-driven report fetching with a shared date-range selector component and standard GET form submission. There is no indication of a security fix or vulnerability being addressed.

This commit fixes how a custom date range is displayed and submitted in BTCPay Server's web interface. It changes the way the browser's timezone is sent back to the server and how date/time inputs are pre-filled. There is no clear security bug being fixed; it appears to be a user-experience and correctness improvement for date filtering.

This commit is a straightforward user-interface convenience change: it adds a 'Manage Labels' link inside the label dropdown on wallet transaction and payment request pages. There is no security-relevant behavior change in the diff itself.

This is a large UI refactoring commit that improves date range filtering, search components, and label selectors across BTCPay Server's admin pages. It replaces timezone-offset handling with named timezone handling, restructures how search filters are parsed and stored, and adds shared view components. There is no clear security fix or vulnerability being patched; it appears to be a feature/refactoring change.

This commit fixes a localization bug in BTCPay Server's Blazor user interface components. Some text strings were not being translated into the user's chosen language because they relied on a translation mechanism that only works in older Razor view files, not in newer Blazor components. The change switches those strings to use Blazor-compatible localization and registers the new translatable phrases in the default translation file. There is no security impact.