BTCPay Server

This commit is a minor cleanup: it changes how an 'empty transactions' message is created on a wallet page. Previously the message was stored as a chunk of HTML in translation files; now it is built safely in code with plain text. There is no security issue here—just a small improvement in how the page is assembled.

This commit only updates the list of translatable text strings in BTCPay Server. It adds, removes, and reorders phrases used by the application's user interface. There are no code logic changes, no security fixes, and no behavior changes.

This commit removes code that restricted cross-frame messaging to a specific trusted website origin. It now allows messages from any origin ('*') when sending, and only accepts messages from frames with an 'opaque' (null) origin when receiving. This appears to be a security cleanup that reduces the risk of malicious plugin frames tricking the host into trusting their origin, but the change is partial and the full context is unclear without more references.

This commit refactors BTCPay Server's plugin management into a dedicated plugin and adds an embedded plugin directory that loads content from an external plugin catalog via an iframe. The change moves plugin URLs from the server settings area to a new plugin area, adds URL sanitization for author and documentation links, and introduces checks to prevent installing mismatched plugin identifiers. It is a feature/refactoring commit rather than a disclosed security fix, though it includes some defensive hardening.

This commit only changes a code style setting in the project's .editorconfig file. It tells developers to prefer shorter expression-bodied method syntax when it fits on one line. There is no functional code change, no bug fix, and no security relevance.

This commit adds a feature that lets BTCPay Server users import wallet labels from a BIP-329 file. The code parses uploaded JSONL files, validates entries, and attaches labels to transactions, addresses, or transaction outputs. The change is a normal feature addition; there is no direct evidence in the commit that it fixes a security vulnerability, but it does introduce a new file-upload and parsing path that should be reviewed for robustness.

This commit adds right-to-left (RTL) language support to BTCPay Server. It introduces metadata tracking for whether a language is RTL, fetches that flag from the translation manifest, stores it in the database, and switches the user interface to RTL-specific CSS stylesheets when an RTL language like Arabic is active. There is no security issue visible in the change.

This commit is a routine UI refactor: it renames the internal ASP.NET Core view component from <vc:breadcrumb> to <vc:title-header>, updates CSS class names, and standardizes how page titles are set across many Razor views. There is no security-relevant change in behavior—no new endpoints, no permission changes, no input handling changes, and no fixes for injection or bypass issues.

This commit is a routine user-interface cleanup. It replaces many copies of hand-written breadcrumb navigation HTML across the application with a single shared 'Breadcrumb' view component. There is no security-relevant change here—only the way page headers and navigation links are rendered.

This commit reorganizes internal documentation for AI coding assistants. It moves existing developer guidance from one file into separate 'skill' files and adds new style guides for frontend naming and test writing. No application code, configuration, or user-facing behavior was changed.

This commit is mostly a code cleanup and test-helper refactor. It introduces a shared test helper for search filters, switches many HTML IDs to CSS classes for easier testing, fixes a duplicate date-range filter bug, and changes a Telegram footer link from t.me to telegram.me. There is no clear security vulnerability in the diff, and the changes appear to be routine maintenance.

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.

This commit fixes a bug in BTCPay Server's plugin system where a safety check that prevents directory traversal attacks was accidentally rejecting valid plugin names on Windows. The original code always appended a '/' slash, but Windows uses '\' as its path separator, so the safety check compared paths with mismatched slashes and falsely flagged them as attacks, causing a crash. The fix makes the trailing slash match the operating system's separator. There is no direct evidence in the commit that an actual security vulnerability was exploited; it appears to be a bug fix for a false-positive crash.

This commit removes Bootstrap tooltip attributes from a few disabled buttons and archive links in the invoice view. It is a test-flakiness fix with no apparent security relevance.

This commit only adds a link to a blog post announcement in the changelog. It contains no code changes, no security fixes, and no functional modifications.