BTCPay Server

This is a small user-interface bug fix. When a user scanned a QR code with their camera to provide a PSBT (a partially signed Bitcoin transaction), the on-screen modal dialog failed to close for multisig transactions because the JavaScript was clicking the wrong button. The patch makes the code click the correct button so the modal closes as expected. There is no security vulnerability here.

This commit simply adds 'Norwegian' as a new language option in a dropdown list inside an administrative view. There is no security relevance: no code logic, permissions, data handling, or user input processing changed.

This commit adds a CI safety check that refuses to build Docker images unless the current Git commit has a valid GPG signature. It is a hardening improvement, not a fix for an active vulnerability. There is no indication in the commit or title that it responds to a known security incident.

This commit is a simple user-interface fix: it moves a checkbox setting ('Disable zero amount invoices') so it appears in the correct section of the Point of Sale settings page. The setting was previously only shown under the 'Keypad' section, but it should be visible for all Point of Sale types. There is no security issue here.

This commit is a routine version bump and changelog update for BTCPay Server 2.3.2. It does not change any application code, only the version number and release notes. The changelog describes bug fixes and a new feature, but those actual code changes are not present in this diff.

This commit adds a new optional setting for BTCPay Server's Point of Sale (PoS) app that lets store owners block invoices with a zero total amount. Previously, a customer could complete a checkout flow that created an invoice worth nothing, which could be used to generate fake or confusing payment records, test transactions, or possibly abuse downstream systems that expect only paid invoices. The change is a defensive feature, not a fix for a known active attack, and it is disabled by default.

This commit removes an unused or redundant 'Id' property from a checkout view model in the Subscriptions plugin. The property was being set from a plan identifier but appears to have been 'confusing' rather than functional. There is no indication in the commit that this change fixes a security vulnerability.

This commit removes one configuration line ('auto_resolve_threads: true') from the project's CodeRabbit AI code-review settings file. It does not change any application code, payment logic, authentication, API behavior, or anything users interact with. There is no security relevance.

This commit corrects a spelling mistake in the project's changelog, changing 'upgradding' to 'upgrading'. It does not modify any program code, configuration, or documentation that affects how the software runs or behaves.

This commit changes how BTCPay Server handles crashes caused by plugins during startup. Previously, if a plugin caused a crash, the server would try to disable just that one plugin. The new code can disable all plugins when the server cannot tell which specific plugin is at fault, and it also avoids disabling built-in 'system' plugins. This is a reliability and recovery improvement rather than a fix for a remote attack.