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 · a080c0c8 · Jan 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 a test file and adds a test marker to a UI message. It makes an automated browser test more reliable by waiting for elements to appear and checking their text in a more stable way. There is no security relevance.
AI review queuedSigned commitby Nicolas Dorier · 9d98f33d · Jan 13, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Signed commit
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! 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 commit removes one blank line from a database migration file. It is a cosmetic formatting change with no functional or security effect.
AI review queuedBump to 2.3.3by Nicolas Dorier · 12186ac8 · Jan 13, 2026 · 3 filesMessage 38 · OpaqueInformational 17Details
Commit message · Nicolas Dorier
Bump to 2.3.3
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 17/100
This commit is a routine version bump from 2.3.2 to 2.3.3 for the BTCPay Server project. It updates the version number, adds a changelog entry describing new features and bug fixes, and adds a single debug log line to a test. The commit itself does not contain any application code changes that would fix or introduce a security vulnerability. The changelog mentions several bug fixes, but none are described by the vendor as security issues, and no independent security references are provided.
AI review queuedBump to 2.3.3by Nicolas Dorier · afa97b62 · Jan 13, 2026 · 3 filesMessage 38 · OpaqueInformational 16Details
Commit message · Nicolas Dorier
Bump to 2.3.3
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 16/100
This commit is a routine version bump to 2.3.3 for the BTCPay Server project. It updates the version number, adds a changelog entry, and adds a single debug log line in a test file. The changelog describes several bug fixes and one notable change: CoinGecko rate sources are removed because CoinGecko now requires an API key. None of the changes in the diff itself are security fixes or introduce security-relevant code.
AI review queuedUpdate translationsby Nicolas Dorier · b807ed2f · Jan 11, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Update translations
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
This commit only updates the default translation strings file in BTCPay Server. It adds, removes, and rewords user-facing text labels (for example, new labels for monetization features, language packs, and payment request labels). There are no code logic changes, no security fixes, and no changes to how the application behaves.
AI review queuedFix: Selecting some rate source would crash the Stores/Rates page (#7095)by Nicolas Dorier · 208f45dc · Jan 10, 2026 · 5 filesMessage 70 · AdequateLow 27Details
Commit message · Nicolas Dorier
Fix: Selecting some rate source would crash the Stores/Rates page (#7095)
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 27/100
This commit fixes a bug where choosing certain cryptocurrency exchange rate sources would crash the BTCPay Server 'Stores/Rates' settings page. The root cause was that some rate source IDs contained characters like dashes or dots that are not valid in C# identifiers, which caused the rate-rule parser to throw an exception and crash the page. The fix adds validation when creating rate-source IDs, changes one provider's ID to remove a hyphen, sanitizes several IDs in a large exchange list, and makes the controller gracefully fall back when a preferred source cannot be found or parsed.
Security candidateFeature: Cold wallet transaction support via Greenfield API (#7068)by Nicholas Halka · 8a30dd1e · Jan 9, 2026 · 7 filesMessage 91 · StrongLow 32Details
Commit message · Nicholas Halka
Feature: Cold wallet transaction support via Greenfield API (#7068)
* Enables unsigned PSBT transaction creation
Adds support for creating unsigned PSBT transactions, facilitating multisig withdrawal workflows. Introduces a new API endpoint for broadcasting on-chain transactions. Enhances transaction creation to allow opting out of server-side signing.
* Update Docs And Tests
* Removes Unused Transaction field from PSBT creation response
91/100 · StrongMessage clarity
✓ Specific, 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 boundarysigning or wallet path
AI analysis · Low 32/100
This commit adds new API features to BTCPay Server so users can create unsigned Bitcoin transactions (PSBTs) and broadcast already-signed transactions through the Greenfield API. It is a feature addition, not a bug fix. The code does not appear to introduce an obvious vulnerability, but it changes how wallet transactions are authorized and signed, which is security-sensitive. There is no vendor statement or external report saying this commit fixes a security issue.
Security candidateFix: PSBT Scan via Camera was not closing the modal dialog when signing a multisig transaction (#7089)by Nicolas Dorier · 1787e9d2 · Jan 9, 2026 · 1 fileMessage 70 · AdequateInformational 18Details
Commit message · Nicolas Dorier
Fix: PSBT Scan via Camera was not closing the modal dialog when signing a multisig transaction (#7089)
Fix #6925
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
signing boundarysigning or wallet pathparser or protocol path
AI analysis · Informational 18/100
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.
AI review queuedAdd norvegian langby Nicolas Dorier · d082ea7c · Jan 7, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Add norvegian lang
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 '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.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarydefensive validationsigning or wallet path
AI analysis · Informational 15/100
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.
Security candidateFix: Disable zero amount invoices in PoS doesn't show for Keypad (#7071)by Nicolas Dorier · a4034860 · Jan 3, 2026 · 1 fileMessage 70 · AdequateInformational 15Details
Commit message · Nicolas Dorier
Fix: Disable zero amount invoices in PoS doesn't show for Keypad (#7071)
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
boot or update path
AI analysis · Informational 15/100
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.
AI review queuedChangelog 2.3.2by Nicolas Dorier · cb10a6cf · Jan 2, 2026 · 2 filesMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Changelog 2.3.2
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 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.
Security candidatePoS: Can disable zero amount invoices (#7066)by Nicolas Dorier · 884a401d · Jan 2, 2026 · 4 filesMessage 53 · ThinLow 32Details
Commit message · Nicolas Dorier
PoS: Can disable zero amount invoices (#7066)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · Low 32/100
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.
AI review queuedRemove confusing propertyby Nicolas Dorier · db0d3cc3 · Dec 29, 2025 · 2 filesMessage 35 · OpaqueInformational 12Details
Commit message · Nicolas Dorier
Remove confusing property
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 12/100
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.
AI review queuedFix coderabbit warningby Nicolas Dorier · 34b4df0c · Dec 27, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Fix coderabbit warning
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 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.
AI review queuedFix minor typoby Nicolas Dorier · 346e506a · Dec 23, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Fix minor typo
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
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.
AI review queuedDisable all plugins when BTCPay Server crash during startup (#7046)by Nicolas Dorier · fa6107ef · Dec 23, 2025 · 3 filesMessage 58 · ThinLow 31Details
Commit message · Nicolas Dorier
Disable all plugins when BTCPay Server crash during startup (#7046)
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 31/100
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.
AI review queuedbump 2.3.1by Nicolas Dorier · 1c8f8694 · Dec 23, 2025 · 2 filesMessage 0 · OpaqueInformational 21Details
Commit message · Nicolas Dorier
bump 2.3.1
0/100 · OpaqueMessage clarity
! Very short subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 21/100
This commit is a routine version bump from 2.3.0 to 2.3.1 for BTCPay Server, accompanied by a changelog entry. The changelog describes bug fixes for a startup crash loop caused by plugins, lost email settings after an update, and cleanup of monetized subscribers when users are deleted. There are no code changes in this commit that introduce or fix a security vulnerability directly; it is purely a release metadata update.
AI review queuedShow payment request title in wallet transaction tooltip (#6982)by AshwinGajbhiye · d9460daf · Dec 19, 2025 · 3 filesMessage 81 · StrongInformational 19Details
Commit message · AshwinGajbhiye
Show payment request title in wallet transaction tooltip (#6982)
* Apply code formatting
* Show payment request title instead of ID in wallet transaction tooltip
* Fix null safety and data property access for payment request title
* Optimize to fetch all payment requests in a single query
* Simplify payment request tooltip text to 'Payment request:'
* Fix Title
* Remove useless prop
---------
Co-authored-by: Nicolas Dorier <nicolas.dorier@gmail.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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100
This commit is a small UI improvement: when you hover over a wallet transaction that came from a payment request, the tooltip now shows the payment request's human-readable title instead of its internal ID number. It also fetches all related payment requests in one database query rather than one by one. There is no security fix or vulnerability here.
AI review queuedFix flaky testby Nicolas Dorier · 0cad73d4 · Dec 18, 2025 · 1 fileMessage 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 adds a single line to a test file, instructing an automated browser test to wait for an alert message before continuing. It is purely a test stability fix and does not change any production code, user-facing behavior, or security controls.
AI review queuedUpdate Changelogby Nicolas Dorier · 1061261f · Dec 18, 2025 · 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 updates the project's Changelog.md file. It adds and tweaks changelog entries describing bug fixes made in other commits. No source code, configuration, or executable behavior was changed. There is no security relevance in the diff itself.
AI review queuedfixup uneeded conditionby Nicolas Dorier · 5dbc03da · Dec 18, 2025 · 1 fileMessage 28 · OpaqueInformational 11Details
Commit message · Nicolas Dorier
fixup uneeded condition
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 11/100
This is a tiny code cleanup in a background migration service. It removes an unnecessary check (`i.Title != null`) from a database query that selects old-style payment requests needing migration. There is no visible security relevance: the change does not alter access controls, validation, or data handling in a way that would create or fix a vulnerability.
AI review queuedAdd changelogby Nicolas Dorier · e8140567 · Dec 17, 2025 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Add changelog
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
This commit only adds two lines to the project's changelog file describing new features (payment request reports and improved filtering). It contains no code changes, no bug fixes, and no security-related content.
✓ Descriptive subject✓ Names a concrete action or component! 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 routine UI rename and tidy-up. It changes the wallet label deletion page from saying 'Remove' to 'Delete', renames the underlying action method from RemoveWalletLabel to DeleteWalletLabel, and updates the matching URL from /remove to /delete. It also adds a breadcrumb navigation bar and fixes some indentation. There is no security-relevant change.
AI review queuedFix migrationby Nicolas Dorier · c4649083 · Dec 17, 2025 · 3 filesMessage 18 · OpaqueLow 29Details
Commit message · Nicolas Dorier
Fix migration
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 29/100
This commit fixes a database migration for payment requests in BTCPay Server. It changes how a new 'Title' column is populated from existing JSON data and adjusts the in-code migration logic. The changes appear to be a bug fix for a migration that previously did not run correctly, rather than a deliberate security patch. There is no clear evidence of an exploitable vulnerability in the diff itself.