Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
53/100 average clarity
90Strong · 80–100
213Adequate · 60–79
480Thin · 40–59
194Opaque · 0–39
10security candidates with opaque commit messaging
This commit is a simple rename of a code attribute from UseStoreLanguageAttribute to StorefrontRouteAttribute. It only changes the name used in source files and does not alter any program behavior, security settings, or access controls.
This commit changes how the invoice checkout page is translated. Instead of loading translations from separate JSON files in the browser based on a language the customer picks, the page now uses the store's own server-side translation sett…
Removal of client-side language selection reduces attack surface for language-related query-string manipulation (e.g., lang=...)Server-side rendering of checkout strings may reduce exposure to DOM-based XSS via translation files, but no specific vulnerability is shownLarge deletion of locale files and i18next vendor scripts is a cleanup, not a patch
This commit updates two .NET runtime/SDK Docker images to newer patch versions and bumps a third-party library (CsvHelper) from 34.0.0 to 34.1.0. These are routine maintenance updates. The commit message does not say any of the updates fix…
This is a large hardening patch for BTCPay Server that fixes several security weaknesses around account handling, payments, refunds, and plugins. Key changes include: preventing Blazor circuits from staying authenticated after a user's adm…
Blazor circuit principal revalidation against live user stateCookie principal rejection when user is administratively restrictedRefund creation serialized with SELECT FOR UPDATE and single open refund enforcement
20ae3337by Andrew Camilleri (Kukks)+1310−41655 files
This commit removes a per-invoice checkout language option and translates more public-facing text so it can be localized. It is a feature-cleanup and internationalization change, not a security fix. There is no evidence of a vulnerability …
This commit fixes a bug where BTCPay Server's Point of Sale and Crowdfund inventory counts could become wrong after unpaid or expired invoices. Previously, the system could add inventory back multiple times for the same invoice, making it …
Business-logic flaw: inventory counts could be inflated by duplicate restocking eventsState-machine fix: previous status now tracked to prevent double-countingRace/ordering concern mitigated by deterministic event-barrier for tests
This commit fixes a bug in BTCPay Server where marking an already-expired invoice as 'invalid' could cause the app inventory to be restocked twice. The fix tracks each invoice's previous status during status transitions and skips the inven…
Business-logic bug causing duplicate inventory restockingStatus-transition event missing prior-state contextInventory manipulation possible through invoice state changes
This commit adds a new store-level setting that lets merchants choose which language customers see on public pages such as invoices, payment requests, and pull payments. It also marks more text on those pages as translatable. There is no d…
New per-request language scoping via AsyncLocal with explicit BeginRequest/Restore disposalSignalR hub now applies store language to controller calls that bypass MVC filtersRouteStoreResolver centralizes route-value-to-store-id lookup with 10-minute sliding memory-cache
This commit fixes two bugs in BTCPay Server's wallet transaction API. First, when users filtered transactions by both status (confirmed/unconfirmed) and label, the same transaction could appear twice in the results because the filtering lo…
Fixes duplicate entries in API query results due to incorrect filter compositionReplaces unsafe uint256.Parse with uint256.TryParse to prevent unhandled exceptions on malformed inputAdds server-side input validation returning structured 404 API error for invalid transaction IDs
This commit only updates the version tag of the LND (Lightning Network Daemon) Docker image used in test environments from v0.21.7-beta to v0.21.8-beta. It does not change any production application code, configuration logic, or runtime be…
This commit simply bumps the version numbers of three NuGet packages: a test reporting helper and two FIDO2 authentication libraries. There is no indication in the commit itself that these updates fix a security problem, and no external re…
This commit updates many third-party software libraries (NuGet packages) to newer versions and makes small code adjustments so BTCPay Server stays compatible with those updates. The most notable security-relevant change is a rewrite of the…
Dependency version bumps for libraries with known security maintenance value (HtmlSanitizer, Fido2, MailKit, Microsoft.AspNetCore, System.Security.Cryptography.Pkcs)Manual CSV field escaping added to prevent formula/CSV injection in wallet transaction exportsFido2 configuration/AppID handling changed during Fido2 library upgrade
This commit fixes a crash in BTCPay Server's admin page that shows how an API key has been used. The crash happened when an API key had permissions tied to more than one store. The fix also corrects how usage counts are recorded and displa…
Fixes a UI crash in an administrative API-key usage pageCorrects aggregation of permission usage records when permissions are scoped to specific storesChanges database upsert to persist full permission string including store scope
This commit fixes a crash in BTCPay Server's admin page that shows how an API key has been used. The crash happened when the same permission (like 'view invoices') was used for more than one store. The fix also corrects how usage counts ar…
Fixes a runtime crash in an administrative API-key usage viewCorrects aggregation of permission usage records that previously could duplicate or conflate store-scoped entriesChanges upsert to persist full permission string including scope, preventing legacy-style policy-only rows from overwriting each other
This commit fixes a math bug in how BTCPay Server rounds very small negative amounts. Previously, a helper called RoundToSignificant divided by the signed value instead of its absolute value, so negative numbers behaved differently from po…
Rounding/truncation bug in financial amount handlingNegative-amount handling asymmetry that could alter displayed or computed balancesFee-bump calculation could fall below Bitcoin incremental relay fee requirement
This commit fixes a crash in the API key authorization page. When a user submits the form without clicking either the 'Authorize' or 'Cancel' button, the server tries to read a missing command value, which could cause an error. The fix saf…
Null dereference in request handling pathUnhandled exception could lead to error disclosure or availability impactDefensive null-safety hardening in controller action
This commit hardens how BTCPay Server downloads translation files from GitHub. It adds checks so the app only fetches files from the project's own trusted GitHub organization, blocks automatic web redirects, and supports a new optional red…
Server-side request forgery (SSRF) protection added: URI host/path validation before outbound fetchAutomatic HTTP redirects disabled for translation update clientManifest redirect field introduced with same-origin/org trust validation
This commit hardens how BTCPay Server downloads translation files from the internet. It adds checks so the server only fetches language packs and manifest redirects from the trusted btcpayserver GitHub organization, turns off automatic HTT…
Server-side request forgery (SSRF) hardening: URI scheme, host, and path prefix are validated before outbound fetchOpen-redirect / HTTP redirect abuse mitigation: AllowAutoRedirect set to false on the translation HttpClientPath traversal mitigation: pack file paths resolved as relative URIs and validated against trusted org prefix
This commit removes old database upgrade scripts (migrations) from before BTCPay Server version 1.12.0 and replaces them with a single consolidated starting schema. It also trims the startup migration task by deleting obsolete data-convers…
Large-scale deletion of database migration historyConsolidation of cumulative schema into a single init SQL scriptRemoval of legacy data-migration logic from startup task
This commit is a large database cleanup: BTCPay Server removed all old EF Core migration files before version 1.12.0 and replaced them with a single consolidated SQL script that creates the current schema from scratch. It also trims the st…
Large schema consolidation could silently drop or alter constraints/indexes compared to the incremental migration historyRemoval of legacy migration executors means installations upgrading from very old versions must rely on the consolidated init script and any remaining IMigrationExecutor implementationsNo explicit security claim or CVE reference in commit message or diff
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
AI review queuedFix flaky testby Nicolas Dorier · 7be7ff18 · Jul 13, 2026 · 2 filesMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Fix flaky test
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
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.
AI review queuedFix buildby Nicolas Dorier · 9d7e1f3a · Jul 13, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Fix build
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
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.
AI review queuedRemove useless codeby Nicolas Dorier · 61b27b76 · Jul 13, 2026 · 1 fileMessage 28 · OpaqueInformational 12Details
Commit message · Nicolas Dorier
Remove useless code
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 12/100
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.
* Add editable invoice comment metadata and include it in the invoices report export
* Add invoice comment viewing and editing to the details page and invoice list
* Test invoice comment saving, list view, and export
* Use SQL rather than EF
* Add comment to the greenfield API
---------
Co-authored-by: Nicolas Dorier <nicolas.dorier@gmail.com>
86/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathboot or update path
AI analysis · Informational 21/100
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.
AI review queuedBump libby Nicolas Dorier · 88968750 · Jul 13, 2026 · 1 fileMessage 0 · OpaqueInformational 0Details
Commit message · Nicolas Dorier
Bump lib
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 0/100
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.
AI review queuedUnify reports page time range selection (#7438)by Nicolas Dorier · 64fbba6f · Jul 13, 2026 · 16 filesMessage 76 · AdequateInformational 15Details
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
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.
AI review queuedProperly format Custom Range in date range selector (#7439)by Nicolas Dorier · 6c9d715f · Jul 9, 2026 · 7 filesMessage 58 · ThinInformational 18Details
Commit message · Nicolas Dorier
Properly format Custom Range in date range selector (#7439)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100
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.
AI review queuedAdd Manage Labels link to Bitcoin Wallet labels (#7435)by Nicolas Dorier · 6901c0ef · Jul 9, 2026 · 5 filesMessage 58 · ThinInformational 15Details
Commit message · Nicolas Dorier
Add Manage Labels link to Bitcoin Wallet labels (#7435)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
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.
AI review queuedImprove date range filtering and shared search components (#7424)by Nicolas Dorier · 3ec6a984 · Jul 7, 2026 · 62 filesMessage 58 · ThinInformational 24Details
Commit message · Nicolas Dorier
Improve date range filtering and shared search components (#7424)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 24/100
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.
AI review queuedLocalize Blazor strings that the text-translate TagHelper can't reach (#7423)by Wiredancer · 364e6be9 · Jul 7, 2026 · 4 filesMessage 81 · StrongInformational 15Details
Commit message · Wiredancer
Localize Blazor strings that the text-translate TagHelper can't reach (#7423)
`text-translate`/`html-translate` are handled by TranslateTagHelper, an MVC TagHelper that only runs while rendering Razor (.cshtml) views. Blazor components do not execute TagHelpers, so these attributes are inert inside .razor files: the literal English text is always rendered, regardless of the active language.
Switch the affected strings to @StringLocalizer[...] / @ui.StringLocalizer[...], which resolves correctly in Blazor (as already used e.g. for the notifications button tooltip on the very same component):
- NotificationsDropDown.razor: "Notifications", "Mark all as seen", "No new notifications", "View all" - PosLoginCode.razor: "Signed in user", "None, just open the URL" (adds the IStringLocalizer injection) - XPubSelect.razor: "Account"
Also register the newly-translatable strings in Translations.Default.cs.
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 15/100
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.
AI review queuedFix "File traversal detected" crash processing plugin commands on Windows (#7422)by Andrew Camilleri · a8c01be5 · Jul 7, 2026 · 1 fileMessage 58 · ThinLow 33Details
Commit message · Andrew Camilleri
Fix "File traversal detected" crash processing plugin commands on Windows (#7422)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Low 33/100
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.
AI review queuedMake test less flakyby Nicolas Dorier · 7cb03bb3 · Jun 30, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Make test less flaky
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
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.
AI review queuedAdd blog post announcementby Nicolas Dorier · e5c2a4cc · Jun 25, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Add blog post announcement
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
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.
AI review queuedRestore lndhub supportby Nicolas Dorier · cea07e5e · Jun 24, 2026 · 2 filesMessage 28 · OpaqueInformational 16Details
Commit message · Nicolas Dorier
Restore lndhub support
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 16/100
This commit reverts a planned removal of LNDHub support by updating a single Lightning library version and editing the changelog. It is a feature restoration, not a security fix. There is no evidence in the commit of any vulnerability, exploit, or security-relevant change.
AI review queuedFix flaky testby Nicolas Dorier · 23219bc9 · Jun 24, 2026 · 2 filesMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Fix flaky test
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit fixes a flaky automated test for the global search feature. The JavaScript change makes the search run automatically if a query is already present when the search UI opens, and the test code is simplified to remove a special screenshot-on-failure workaround. There is no security issue here.
AI review queuedImprove phoenixd, remove support for deprecated lightning backendby Nicolas Dorier · 009f458e · Jun 19, 2026 · 22 filesMessage 50 · ThinInformational 22Details
Commit message · Nicolas Dorier
Improve phoenixd, remove support for deprecated lightning backend
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 22/100
This commit is a routine maintenance update for BTCPay Server. It removes support for three older/deprecated Lightning payment backends (Lightning Charge, LNDHub, and LNBank), updates the phoenixd integration, bumps a couple of library versions, and adjusts tests accordingly. There is no indication in the commit that this fixes an active security vulnerability or introduces new attack paths.
AI review queuedFix: When a server has too many apps, the Policies page timeout or crash (#7406)by Nicolas Dorier · e6085835 · Jun 17, 2026 · 4 filesMessage 70 · AdequateLow 37Details
Commit message · Nicolas Dorier
Fix: When a server has too many apps, the Policies page timeout or crash (#7406)
70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Low 37/100
This commit fixes a performance problem on the BTCPay Server 'Policies' settings page. Previously, the page tried to load a dropdown list of every app on the server, which could time out or crash when there were many apps. The fix replaces the dropdown with a simple text box where the administrator types an app ID directly. It also adds validation to reject invalid app IDs instead of crashing. The change is primarily a reliability/performance fix, but it slightly changes how app IDs are entered and validated.
AI review queuedAdd missing translationsby Nicolas Dorier · ea692b4a · Jun 15, 2026 · 3 filesMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Add missing translations
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit simply adds missing translated text labels for a global search feature. It changes hardcoded English hint text into references to the project's translation system so the hints can appear in other languages. There is no security relevance.
AI review queuedMissing translationby Nicolas Dorier · 64797ee2 · Jun 15, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Missing translation
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit changes a single user-visible label from a plain English string to a translatable string. It is a routine localization fix with no security relevance.
AI review queuedUpdate Changelogby Nicolas Dorier · b9180fa1 · Jun 15, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Update Changelog
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
This commit only adds one line to the project's changelog, documenting that a bug where Lightning invoices were silently dropped on reconnection has been fixed. The actual code change happened elsewhere, so this commit itself does not modify any program logic or fix any vulnerability directly.
AI review queuedUpdate Changelog.mdby Nicolas Dorier · b991f621 · Jun 12, 2026 · 2 filesMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Update Changelog.md
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit only adds new text strings for a 'bulk archive pull payments' feature and records it in the changelog. There is no code logic change, no security fix, and no behavior that could be exploited. It is a routine localization/changelog update.
AI review queuedUpdate translationby Nicolas Dorier · 90073dde · Jun 11, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Update translation
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
This commit adds a single new translation string to the application's default translation file. It is a localization-only change with no security relevance.
AI review queuedRemove useless codeby Nicolas Dorier · 89626c03 · Jun 11, 2026 · 3 filesMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Remove useless code
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit removes database-provider checks from two old database migration files and adds developer instructions for creating future migrations. It does not change application behavior for users, fix a vulnerability, or introduce new functionality. The SQL inside the migrations is unchanged; it now simply runs unconditionally rather than only when PostgreSQL is detected.
AI review queuedUpdate changelogby Nicolas Dorier · 696537d5 · Jun 11, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Update changelog
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
This commit only adds a single line to the project's changelog, documenting that a missing 'Uninstall' button for language packs was fixed. It changes no program code, configuration, or executable files, so it cannot by itself introduce or fix any security issue.
AI review queuedBuild cahsu-pluginby Nicolas Dorier · 31936c7a · Jun 10, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Build cahsu-plugin
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit adds a new third-party plugin called 'cashu-plugin' to BTCPay Server's automated compatibility-check script. The script clones the plugin's repository, initializes its submodule, wires it against the current BTCPay Server code, and builds it in CI. There is no code change to BTCPay Server itself, no bug fix, and no security-related content in the commit message or diff.