Package v0.2.12→v0.2.124: manifest, actions, version graph

startos/versions/v0.2.73.ts

@@ -0,0 +1,13 @@
+import { VersionInfo } from '@start9labs/start-sdk'
+
+export const v_0_2_73 = VersionInfo.of({
+  version: '0.2.73:0',
+  releaseNotes: {
+    en_US:
+      "Fix the BTCPay 2.x payment-method detection. The /payment-methods response field was renamed from `paymentMethod` to `paymentMethodId` in BTCPay 2.x, and the heuristic shipped in v0.2.71 was checking the legacy 1.x name only — so it never matched on stores running 2.x and the inline-Lightning path silently fell back to the BTCPay redirect. The picker now checks both field names. Also: when a store has both BTC-LN (BOLT11-direct) and BTC-LNURL methods, we prefer BTC-LN — every Lightning wallet supports BOLT11 but LNURL-pay needs a capable wallet (and BTCPay's LNURL entry often has a null destination until the buyer scans, which we can't render to a QR). Skips entries with null/empty destinations.",
+  },
+  migrations: {
+    up: async ({ effects }) => {},
+    down: async ({ effects }) => {},
+  },
+})