@gadicc/loom 2.2.0 → 2.2.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.
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"version": 1,
|
|
3
|
-
"supportDigest": "
|
|
3
|
+
"supportDigest": "47a228d08d384f1c47946808ea121e2dc47571a71585353dad5b588652337c57",
|
|
4
4
|
"supportSources": [
|
|
5
5
|
"src/apiKeys/betterAuth.ts",
|
|
6
6
|
"src/apiKeys/permissions.ts",
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@gadicc/loom",
|
|
3
|
-
"version": "2.2.
|
|
3
|
+
"version": "2.2.1",
|
|
4
4
|
"description": "Shared helpers and verification tooling for Next.js applications.",
|
|
5
5
|
"homepage": "https://github.com/gadicc/loom#readme",
|
|
6
6
|
"repository": {
|
|
@@ -11,7 +11,7 @@
|
|
|
11
11
|
"url": "https://github.com/gadicc/loom/issues"
|
|
12
12
|
},
|
|
13
13
|
"loom": {
|
|
14
|
-
"gitCommit": "
|
|
14
|
+
"gitCommit": "503df2e7b0535b868fa7b5ae58044834cc40c1b0"
|
|
15
15
|
},
|
|
16
16
|
"type": "module",
|
|
17
17
|
"main": "./esm/mod.js",
|
|
@@ -57,6 +57,10 @@ changing the target repository.
|
|
|
57
57
|
migrations, smoke-test it, and only then promote it. Keep automatic preview
|
|
58
58
|
deployments, but disable automatic `main` production deployments once that
|
|
59
59
|
release workflow is ready.
|
|
60
|
+
- For new GitHub release workflows, use short-lived GitHub OIDC through Vercel
|
|
61
|
+
Trusted Sources for protected HTTP checks. Read the Loom release safety and
|
|
62
|
+
Trusted Sources references before writing the workflow. Deployment/promotion
|
|
63
|
+
still needs its separate bounded Vercel API credential.
|
|
60
64
|
- Keep secrets out of commits, command arguments, logs, caches, and uploaded
|
|
61
65
|
artifacts. Document variable names in `.env.example`.
|
|
62
66
|
|
|
@@ -187,6 +187,14 @@ Set the chosen Vercel function region in `vercel.json`. For a DB-backed app,
|
|
|
187
187
|
build the GitHub-to-Vercel staged release before disabling Vercel's automatic
|
|
188
188
|
production deployment for `main`.
|
|
189
189
|
|
|
190
|
+
Before writing release steps, read
|
|
191
|
+
[Loom release safety](../../loom/references/release-safety.md) and
|
|
192
|
+
[Trusted Sources adoption](../../loom/references/release-trusted-sources.md).
|
|
193
|
+
For a new GitHub workflow, choose GitHub OIDC for protected HTTP checks; the
|
|
194
|
+
legacy create/check/revoke bypass sequence remains compatibility guidance for
|
|
195
|
+
existing apps. OIDC does not replace deployment/promotion API authentication,
|
|
196
|
+
database migration credentials, or normal application sign-in.
|
|
197
|
+
|
|
190
198
|
Use Loom's setup commands where applicable:
|
|
191
199
|
|
|
192
200
|
```text
|
|
@@ -206,8 +214,23 @@ The app-local workflow must:
|
|
|
206
214
|
6. build and scan the exact prebuilt artifact;
|
|
207
215
|
7. upload it with `--prebuilt --prod --skip-domain`;
|
|
208
216
|
8. run the backward-compatible Drizzle migration;
|
|
209
|
-
9.
|
|
210
|
-
|
|
217
|
+
9. verify the immutable deployment's project, owner, and source identity, then
|
|
218
|
+
smoke-test it using `createGithubActionsOidcFetch` from `@gadicc/loom/release`;
|
|
219
|
+
10. promote that exact deployment and verify its canonical alias through OIDC.
|
|
220
|
+
|
|
221
|
+
Use `loom db release trust-plan`, review its exact repository ID/name, branch,
|
|
222
|
+
GitHub environment, workflow, audience, and target Vercel environment, then apply
|
|
223
|
+
and verify the reviewed plan within the user's authorization. Grant the HTTP
|
|
224
|
+
check job `id-token: write`; keep the deployment API token out of HTTP-only steps.
|
|
225
|
+
Prove real allowed and denied identities in read-only acceptance jobs before
|
|
226
|
+
claiming the OIDC setup works. Do not deploy, migrate, or promote from those jobs.
|
|
227
|
+
|
|
228
|
+
A missing GitHub link blocks identity-bound trust planning; it does not change
|
|
229
|
+
the recommended HTTP transport. Complete the authorized repository link or report
|
|
230
|
+
that prerequisite, and keep release promotion gated until OIDC acceptance passes.
|
|
231
|
+
Do not silently scaffold a bypass fallback just because linking is unfinished.
|
|
232
|
+
For an existing app that retains a bypass, preserve create/check/revoke cleanup
|
|
233
|
+
on every failure path until its deliberate OIDC migration passes acceptance.
|
|
211
234
|
|
|
212
235
|
Keep preview deployments automatic. Pin third-party Actions to reviewed full
|
|
213
236
|
commit SHAs and let Dependabot maintain them.
|