BTCPay Server

This commit adds a public PGP key file and updates a CI script to import it when verifying that commits are cryptographically signed. It is a hardening/operational improvement to the project's build verification process, not a fix for a software vulnerability in BTCPay Server itself.

This commit only updates a user-facing help message in the email rules page. It adds a second example placeholder ({Subscriber.Metadata.accessKey}) alongside the existing one ({Invoice.Metadata.itemCode}) to make the documentation clearer. There is no code behavior change and no security relevance.

This commit is a routine cleanup. It removes two unused namespace imports from a webhook trigger provider file and adds null checks and a page-load wait to automated UI tests. There is no change to production logic, no security fix, and no disclosed vulnerability.

This commit changes two lines in a single test file to make a flaky test more reliable. It replaces a broad check that the page contains the text 'Pay123' with a more precise check that a specific element with the expected ID shows the text 'Pay123'. This is a test-quality improvement, not a security fix.

This commit fixes a bug in BTCPay Server's subscription email feature where metadata placeholders for offerings and customers didn't work, and adds a new placeholder for subscriber metadata. The metadata strings are now parsed as JSON objects so email templates can correctly read individual metadata fields. There is no clear security vulnerability here; it is a functional bug fix with a minor side effect that malformed metadata could now cause a parsing error when an email is generated.

This commit only changes an automated UI test file. It adds a helper that checks whether a Bitcoin payment address was correctly filled in after clicking a parse button, and inserts that check plus a screenshot step at three points in the test. There is no change to production code, no user-facing behavior change, and no security fix.

This commit tightens a CI script that checks whether Git commits are cryptographically signed. Previously, the script only rejected commits with status 'N' (no signature). Now it accepts only 'G' (valid trusted signature) or 'U' (valid but untrusted signature) and rejects everything else. This is a hardening improvement, not a fix for an active security flaw.

This commit restores a test that checks whether the project's default translation file is up to date before a release. It does not change production code, fix a bug, or alter security behavior. It is purely a quality-assurance test for translation data.

This commit only adds new translation strings (empty placeholder entries for future localization) to a single C# file. There are no code logic changes, no security fixes, and no functional behavior changes.

This commit is a routine version bump and changelog update for BTCPay Server 2.3.4. It does not change any application code, only records what changed in the release. There is nothing in the diff that introduces or fixes a security issue by itself.

This commit adds a new 'deliveryTime' field to BTCPay Server's webhook API responses and updates the related documentation and invoice UI wording. It exposes when a webhook was actually sent, separate from when it was scheduled. There is no indication this change fixes or introduces a security vulnerability; it appears to be a transparency/usability improvement.

This commit only changes test code. It replaces a few brittle checks in automated UI tests with more robust Playwright-style assertions and adds a page-load wait. There is no change to production code, no user-facing behavior change, and no security relevance.

This change hides a dashboard widget called 'Lightning Services' from users who do not have permission to change server settings. Previously, the widget may have been visible to users who lacked those rights, potentially exposing links or information about server-level Lightning services. The fix adds a permission check directly to the widget's HTML wrapper so it only renders for authorized users.

This commit fixes a permission inconsistency in BTCPay Server. Previously, a user who had permission to create Lightning invoices for a store might not have had explicit permission to view those same Lightning invoices. The change makes 'view Lightning invoice' a child permission of 'create Lightning invoice', so anyone who can create them can also see them. This is described as a fix, not a new security vulnerability disclosure, and the diff alone does not show an active exploit or a disclosed incident.

This commit mainly adds the LUNO exchange as the default source for South African Rand (ZAR) exchange rates in BTCPay Server. It also includes a small hardening fix in another rate provider so that missing bid/ask values don't crash the app, plus a batch of unrelated test reliability improvements. There is no clear security vulnerability being patched.