BTCPay Server

This commit is a user-interface redesign, not a security fix. It wraps existing server settings pages into consistent visual sections and adds short explanatory subtitles. No code handling payments, authentication, permissions, or data validation was changed.

This commit simply renames the search feature's 'Keywords' field to 'Aliases' across the BTCPay Server codebase. It is a non-functional refactoring that does not change any security behavior, access controls, or data handling. Backward compatibility is preserved with an obsolete property that maps to the new name.

This commit adds a missing safety check in the API key authorization flow. Previously, if a user clicked a 'confirm' action for an API key that no longer existed, the code would try to use a null (non-existent) key object, which could cause a server crash or unexpected behavior. Now the code checks whether the key exists first and shows an error message if it doesn't.

This commit simply updates four external software library (NuGet package) versions to newer patch releases. There are no code changes shown, and the commit message gives no indication that any security issue is being fixed. It looks like a routine dependency refresh.

This commit changes how BTCPay Server handles a missing user when an administrator tries to resend a verification email. Previously, the code threw a generic internal error (ApplicationException), which could expose internal details or produce an unhandled error page. Now it returns a clean 'Not Found' response. This is a hardening fix: it improves error handling and reduces information leakage, but it does not by itself grant an attacker new capabilities.

This commit adds a simple build-and-publish helper script for the project's NuGet package. It packages the BTCPayServer.Client library, pushes it to the public NuGet registry using an API key from an environment variable, and creates a matching Git tag. There is no indication this change fixes or introduces a security issue; it is a routine developer tooling addition.

This commit fixes a potential cross-site scripting (XSS) issue in BTCPay Server's wallet status messages. When a payjoin transaction fails, the server shows a warning message that includes an error string. Previously, that error string was inserted directly into the HTML of the status message, so if an attacker could influence the error text to contain malicious code (for example, through a script tag), it could run in the administrator's browser. The change now encodes the error text so that any HTML-like characters are displayed as plain text instead of being interpreted as code.

This commit fixes a bug in BTCPay Server's LNURL feature for pull payments. Previously, if someone requested a LNURL for a pull payment that didn't exist, the code would try to use a null (empty) pull payment object, which could cause the server to crash or behave unpredictably instead of returning a simple 'not found' error. The fix adds a check to return 'not found' if the pull payment is missing.