@12-apps/prisma 6.3.0 → 6.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@12-apps/prisma",
|
|
3
|
-
"version": "6.3.
|
|
3
|
+
"version": "6.3.1",
|
|
4
4
|
"description": "Prisma host: the multi-file schema folder, the plugin migration seam, and the shared PrismaClient singleton with its audit / append-only extensions",
|
|
5
5
|
"main": "dist/index.js",
|
|
6
6
|
"types": "dist/index.d.ts",
|
|
@@ -65,22 +65,22 @@
|
|
|
65
65
|
"pglite-prisma-adapter": "0.7.2"
|
|
66
66
|
},
|
|
67
67
|
"devDependencies": {
|
|
68
|
-
"@12-apps/audit": "^5.0
|
|
69
|
-
"@12-apps/auth": "^2.
|
|
70
|
-
"@12-apps/discounts": "^1.
|
|
71
|
-
"@12-apps/entitlements": "^3.
|
|
72
|
-
"@12-apps/entity-lifecycle": "^4.
|
|
68
|
+
"@12-apps/audit": "^5.2.0",
|
|
69
|
+
"@12-apps/auth": "^2.11.0",
|
|
70
|
+
"@12-apps/discounts": "^1.9.0",
|
|
71
|
+
"@12-apps/entitlements": "^3.4.0",
|
|
72
|
+
"@12-apps/entity-lifecycle": "^4.10.0",
|
|
73
73
|
"@12-apps/eslint-config": "^1.21.1",
|
|
74
|
-
"@12-apps/feature-flags": "^2.
|
|
74
|
+
"@12-apps/feature-flags": "^2.2.0",
|
|
75
75
|
"@12-apps/jobs": "^4.4.0",
|
|
76
|
-
"@12-apps/mcp": "^3.
|
|
77
|
-
"@12-apps/notifications": "^4.
|
|
78
|
-
"@12-apps/onboarding": "^2.
|
|
79
|
-
"@12-apps/payments-backend": "^4.
|
|
80
|
-
"@12-apps/product-research": "^2.
|
|
81
|
-
"@12-apps/rbac": "^4.
|
|
82
|
-
"@12-apps/realtime": "^2.
|
|
83
|
-
"@12-apps/report-builder": "^5.
|
|
76
|
+
"@12-apps/mcp": "^3.11.0",
|
|
77
|
+
"@12-apps/notifications": "^4.4.0",
|
|
78
|
+
"@12-apps/onboarding": "^2.4.0",
|
|
79
|
+
"@12-apps/payments-backend": "^4.19.1",
|
|
80
|
+
"@12-apps/product-research": "^2.6.0",
|
|
81
|
+
"@12-apps/rbac": "^4.7.0",
|
|
82
|
+
"@12-apps/realtime": "^2.4.0",
|
|
83
|
+
"@12-apps/report-builder": "^5.12.0",
|
|
84
84
|
"@12-apps/shift": "^3.3.0",
|
|
85
85
|
"@12-apps/typescript-config": "^1.20.1",
|
|
86
86
|
"@types/node": "^22.10.6",
|
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
-- @12-apps/payments-backend owned migration: remember the activation charge
|
|
2
|
+
-- that is currently OUTSTANDING, so a refresh does not charge the owner twice
|
|
3
|
+
-- (FUT-463).
|
|
4
|
+
--
|
|
5
|
+
-- The attempt lived in React state. Refreshing the settings page — or simply
|
|
6
|
+
-- coming back to the tab after paying on the provider's own site, which is
|
|
7
|
+
-- what the flow ASKS the owner to do — erased it and offered to generate a
|
|
8
|
+
-- charge again. That mints a SECOND real charge on their card, while the
|
|
9
|
+
-- first, already paid, is never looked at again.
|
|
10
|
+
--
|
|
11
|
+
-- It also has to carry what confirmation needs and creation is the only chance
|
|
12
|
+
-- to learn. InfinitePay's `payment_check` takes `handle`, `order_nsu`,
|
|
13
|
+
-- `transaction_nsu` and `slug`; `slug` (the invoice code) comes back only in
|
|
14
|
+
-- the response that mints the link. Asking with the reference alone answers
|
|
15
|
+
-- "not paid" indefinitely — which is what happened to a genuinely paid
|
|
16
|
+
-- R$ 1,01, right up to the ten-minute timeout that then told the owner they
|
|
17
|
+
-- had not paid in time.
|
|
18
|
+
--
|
|
19
|
+
-- Nullable, no backfill, no row touched: a connection with nothing in flight
|
|
20
|
+
-- is exactly the null case, and any attempt predating this column is one
|
|
21
|
+
-- nobody can confirm anyway.
|
|
22
|
+
--
|
|
23
|
+
-- ## Why this migration is dated a month after the column it adds
|
|
24
|
+
--
|
|
25
|
+
-- `pending_verification` has been in `payments.prisma` since FUT-463 while the
|
|
26
|
+
-- migration that creates it stayed behind in the host that first needed it.
|
|
27
|
+
-- Every other adopter has therefore been generating a client that selects a
|
|
28
|
+
-- column their database does not have — which is every read of
|
|
29
|
+
-- `PaymentProviderConfig`, not merely the ones that touch this field.
|
|
30
|
+
--
|
|
31
|
+
-- The two properties below are what make it safe to ship late, and both are
|
|
32
|
+
-- load-bearing:
|
|
33
|
+
--
|
|
34
|
+
-- * The name is NEW rather than the origin host's. That host applied
|
|
35
|
+
-- `20260731160000_payments_pending_verification` long ago and syncs this
|
|
36
|
+
-- package's migrations into its own folder; reusing the name would replace
|
|
37
|
+
-- an applied migration's body, and Prisma refuses a migration whose
|
|
38
|
+
-- checksum moved after it was applied.
|
|
39
|
+
-- * `IF NOT EXISTS`, because that same host will now apply THIS file too and
|
|
40
|
+
-- already has the column. Applying a plugin's migrations over a database
|
|
41
|
+
-- that already satisfies them is the ordinary case a host's `migrate
|
|
42
|
+
-- deploy` must survive, not an error.
|
|
43
|
+
ALTER TABLE "payment_provider_configs"
|
|
44
|
+
ADD COLUMN IF NOT EXISTS "pending_verification" JSONB;
|
|
@@ -35,6 +35,7 @@
|
|
|
35
35
|
"20260819230000_auth_email_password",
|
|
36
36
|
"20260820120000_add_user_feature_grants",
|
|
37
37
|
"20260821120000_shift_kind_host_vocabulary",
|
|
38
|
-
"20260821140000_discounts_package_owned"
|
|
38
|
+
"20260821140000_discounts_package_owned",
|
|
39
|
+
"20260824120000_payments_pending_verification"
|
|
39
40
|
]
|
|
40
41
|
}
|