@gadicc/loom 1.15.5 → 1.16.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/db/drizzle-config.d.ts +2 -1
- package/db/drizzle-config.js +6 -3
- package/esm/src/cli/migrationEnv.d.ts +21 -0
- package/esm/src/cli/migrationEnv.d.ts.map +1 -0
- package/esm/src/cli/migrationEnv.js +56 -0
- package/esm/src/cli/mod.d.ts +12 -0
- package/esm/src/cli/mod.d.ts.map +1 -1
- package/esm/src/cli/mod.js +216 -10
- package/esm/src/cli/vercelBuildEnv.d.ts +30 -0
- package/esm/src/cli/vercelBuildEnv.d.ts.map +1 -0
- package/esm/src/cli/vercelBuildEnv.js +186 -0
- package/package.json +2 -2
- package/script/src/cli/migrationEnv.d.ts +21 -0
- package/script/src/cli/migrationEnv.d.ts.map +1 -0
- package/script/src/cli/migrationEnv.js +60 -0
- package/script/src/cli/mod.d.ts +12 -0
- package/script/src/cli/mod.d.ts.map +1 -1
- package/script/src/cli/mod.js +217 -10
- package/script/src/cli/vercelBuildEnv.d.ts +30 -0
- package/script/src/cli/vercelBuildEnv.d.ts.map +1 -0
- package/script/src/cli/vercelBuildEnv.js +191 -0
- package/skills/loom/SKILL.md +9 -2
- package/skills/loom-db/SKILL.md +23 -9
package/skills/loom-db/SKILL.md
CHANGED
|
@@ -29,9 +29,9 @@ Use this skill when working on the shared DB stack from a consuming app.
|
|
|
29
29
|
should use the app's env-aware package scripts or
|
|
30
30
|
`pnpm exec loom env -- <command>`. Do not add `dotenv` or `@next/env` imports
|
|
31
31
|
to implementation files.
|
|
32
|
-
- `createDrizzleConfig()` prefers `
|
|
33
|
-
|
|
34
|
-
|
|
32
|
+
- `createDrizzleConfig()` prefers `MIGRATION_DATABASE_URL_UNPOOLED`, then
|
|
33
|
+
`MIGRATION_DATABASE_URL`, before the gradual-adoption fallbacks
|
|
34
|
+
`DATABASE_URL_UNPOOLED` and `DATABASE_URL`.
|
|
35
35
|
- App-specific fixture table selection, extra Valibot refinements, and auth
|
|
36
36
|
integration should stay local unless they are being extracted deliberately.
|
|
37
37
|
|
|
@@ -73,15 +73,29 @@ Use this skill when working on the shared DB stack from a consuming app.
|
|
|
73
73
|
uploads a staged production deployment with `--prebuilt --prod --skip-domain`,
|
|
74
74
|
runs `db:migrate`, and then promotes the staged deployment. Before adding
|
|
75
75
|
build-only placeholders, preserve an untouched copy of the pulled env file for
|
|
76
|
-
migrations.
|
|
77
|
-
separately governed GitHub Environment secret
|
|
78
|
-
and
|
|
79
|
-
|
|
80
|
-
|
|
76
|
+
migrations. Before Vercel database variables become Sensitive, provide a
|
|
77
|
+
separately governed direct migration URL as the GitHub Environment secret
|
|
78
|
+
`MIGRATION_DATABASE_URL_UNPOOLED` and expose it only to validation and
|
|
79
|
+
migration steps. `vercel pull` and `vercel env run` cannot recover Sensitive
|
|
80
|
+
values. The pulled URL and legacy `DATABASE_URL_UNPOOLED` secret remain
|
|
81
|
+
supported during gradual adoption. Pass `--scope "$VERCEL_ORG_ID"` to Vercel
|
|
82
|
+
CLI release commands so multi-account CI jobs do not resolve the wrong team.
|
|
81
83
|
- Query Vercel Production variable metadata before an external build. Preserve
|
|
82
84
|
usable pulled values, insert unique placeholders only for confirmed unreadable
|
|
83
85
|
Sensitive values, and scan `.vercel/output` for those markers before uploading
|
|
84
|
-
the prebuilt artifact.
|
|
86
|
+
the prebuilt artifact. Prefer `loom db release prepare-build-env` and
|
|
87
|
+
`loom db release verify-build-env`; keep only the declarative requirements
|
|
88
|
+
policy app-local.
|
|
89
|
+
- Use
|
|
90
|
+
`loom db migrations verify-env --env-file
|
|
91
|
+
"$RUNNER_TEMP/vercel-production.env"`
|
|
92
|
+
before a release migration. It validates the preserved pull snapshot plus any
|
|
93
|
+
process-level migration-secret overlay, including URL precedence, database
|
|
94
|
+
role, and direct-vs-pooled endpoint, without printing credentials.
|
|
95
|
+
- Once a dedicated direct URL has been provisioned, load it as
|
|
96
|
+
`MIGRATION_DATABASE_URL_UNPOOLED` in the local process and run
|
|
97
|
+
`loom db migrations setup-github`. Loom sends the value to GitHub over stdin,
|
|
98
|
+
records `LOOM_MIGRATION_DATABASE_ROLE`, and does not change Vercel variables.
|
|
85
99
|
- Use `loom check --network` after wiring a production release workflow so Loom
|
|
86
100
|
can verify the linked Vercel project plus GitHub's `VERCEL_TOKEN`,
|
|
87
101
|
`VERCEL_ORG_ID`, and `VERCEL_PROJECT_ID` release configuration.
|