@quickback-dev/cli 0.66.8 → 0.66.9

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.
Files changed (74) hide show
  1. package/dist/commands/build.d.ts.map +1 -1
  2. package/dist/commands/build.js +11 -1
  3. package/dist/commands/build.js.map +1 -1
  4. package/dist/commands/build.test.js +53 -2
  5. package/dist/commands/build.test.js.map +1 -1
  6. package/dist/commands/canary.d.ts +17 -5
  7. package/dist/commands/canary.d.ts.map +1 -1
  8. package/dist/commands/canary.js +34 -24
  9. package/dist/commands/canary.js.map +1 -1
  10. package/dist/commands/canary.test.d.ts +2 -0
  11. package/dist/commands/canary.test.d.ts.map +1 -0
  12. package/dist/commands/canary.test.js +100 -0
  13. package/dist/commands/canary.test.js.map +1 -0
  14. package/dist/commands/deploy.d.ts +14 -1
  15. package/dist/commands/deploy.d.ts.map +1 -1
  16. package/dist/commands/deploy.js +49 -19
  17. package/dist/commands/deploy.js.map +1 -1
  18. package/dist/commands/deploy.test.d.ts +2 -0
  19. package/dist/commands/deploy.test.d.ts.map +1 -0
  20. package/dist/commands/deploy.test.js +139 -0
  21. package/dist/commands/deploy.test.js.map +1 -0
  22. package/dist/index.js +3 -3
  23. package/dist/lib/compile-next-steps.d.ts.map +1 -1
  24. package/dist/lib/compile-next-steps.js +12 -5
  25. package/dist/lib/compile-next-steps.js.map +1 -1
  26. package/dist/lib/deployment-target.d.ts +29 -0
  27. package/dist/lib/deployment-target.d.ts.map +1 -0
  28. package/dist/lib/deployment-target.js +46 -0
  29. package/dist/lib/deployment-target.js.map +1 -0
  30. package/dist/lib/deployment-target.test.d.ts +2 -0
  31. package/dist/lib/deployment-target.test.d.ts.map +1 -0
  32. package/dist/lib/deployment-target.test.js +27 -0
  33. package/dist/lib/deployment-target.test.js.map +1 -0
  34. package/dist/lib/neon-canary.d.ts +4 -0
  35. package/dist/lib/neon-canary.d.ts.map +1 -1
  36. package/dist/lib/neon-canary.js +24 -4
  37. package/dist/lib/neon-canary.js.map +1 -1
  38. package/dist/lib/neon-canary.test.js +39 -3
  39. package/dist/lib/neon-canary.test.js.map +1 -1
  40. package/dist/lib/neon-target.d.ts +5 -48
  41. package/dist/lib/neon-target.d.ts.map +1 -1
  42. package/dist/lib/neon-target.js +18 -42
  43. package/dist/lib/neon-target.js.map +1 -1
  44. package/dist/lib/neon-target.test.js +26 -4
  45. package/dist/lib/neon-target.test.js.map +1 -1
  46. package/dist/lib/shell.d.ts +10 -0
  47. package/dist/lib/shell.d.ts.map +1 -1
  48. package/dist/lib/shell.js +20 -0
  49. package/dist/lib/shell.js.map +1 -1
  50. package/dist/lib/shell.test.js +35 -1
  51. package/dist/lib/shell.test.js.map +1 -1
  52. package/dist/lib/wrangler-resources.d.ts +1 -1
  53. package/dist/lib/wrangler-resources.d.ts.map +1 -1
  54. package/dist/lib/wrangler-resources.js +20 -9
  55. package/dist/lib/wrangler-resources.js.map +1 -1
  56. package/dist/lib/wrangler-resources.test.js +20 -0
  57. package/dist/lib/wrangler-resources.test.js.map +1 -1
  58. package/dist/schema-engine/index.js +3 -0
  59. package/dist/schema-engine/index.js.map +2 -2
  60. package/dist/schema-engine/provider-dialects.d.ts +1 -1
  61. package/dist/schema-engine/provider-dialects.d.ts.map +1 -1
  62. package/dist/skill/docs/configure/providers.md +18 -3
  63. package/dist/skill/docs/platform/database/index.md +7 -2
  64. package/dist/skill/docs/platform/database/neon.md +37 -2
  65. package/dist/skill/docs/platform/database/planetscale-postgres.md +205 -0
  66. package/dist/skill/docs/start/deploy.md +30 -0
  67. package/dist/skill/docs/tooling/cli.md +41 -0
  68. package/package.json +1 -1
  69. package/src/skill/docs/configure/providers.md +18 -3
  70. package/src/skill/docs/platform/database/index.md +7 -2
  71. package/src/skill/docs/platform/database/neon.md +37 -2
  72. package/src/skill/docs/platform/database/planetscale-postgres.md +205 -0
  73. package/src/skill/docs/start/deploy.md +30 -0
  74. package/src/skill/docs/tooling/cli.md +41 -0
@@ -50,6 +50,7 @@ Run it again any time. When every id is real, there's nothing to create — the
50
50
 
51
51
  | Flag | Effect |
52
52
  |------|--------|
53
+ | `--env <logical-target>` | Select a named target from `environments` (or legacy `providers.database.environments`). Required for named projects. |
53
54
  | `--dry-run` | Print the provisioning plan (what would be created vs. what's already set) and exit. Creates nothing. |
54
55
  | `--skip-deploy` | Provision resources + sync ids + recompile, but skip migrations and the deploy itself. |
55
56
  | `--force` | Overwrite a config id that differs from what Cloudflare reports. Without it, a mismatch prints both values and aborts — never silently overwritten. |
@@ -63,6 +64,35 @@ quickback deploy --dry-run
63
64
  quickback deploy --skip-deploy
64
65
  ```
65
66
 
67
+ ## Named deployment targets
68
+
69
+ ```bash
70
+ quickback deploy --env dev
71
+ quickback deploy --env prod --dry-run
72
+ ```
73
+
74
+ The argument is the **logical config key**. If `dev` declares
75
+ `worker.env: "preview-blue"` and `name: "existing-dev-worker"`, Quickback
76
+ selects `[env.preview-blue]`, migrates only that target's D1 bindings with
77
+ `--env preview-blue`, and uploads that Worker. Top-level bindings are not
78
+ inherited. Both environment placements are supported; declaring both is an
79
+ error. Missing or unknown targets stop before resource creation, migrations,
80
+ or upload.
81
+
82
+ Named targets must already have their D1, KV and Hyperdrive IDs configured in
83
+ their own `worker.bindings`. If an ID is a placeholder, deployment stops before
84
+ provisioning; create that target's resources manually, enter its IDs and run
85
+ `quickback build`. The CLI does not splice named IDs into global provider config.
86
+ R2 buckets declared by the selected target are still ensured by name.
87
+ `--force` does not bypass these checks. `--skip-deploy` skips migrations and
88
+ upload, and `--dry-run` reports without creating resources.
89
+
90
+ Postgres migrations remain a separate operator-owned step, including for named
91
+ Neon targets. `quickback deploy --env dev` selects the Worker but does **not**
92
+ verify that the Hyperdrive origin matches the intended Neon branch, inspect
93
+ remote query caching, or apply Postgres migrations. Configure Hyperdrive with
94
+ query caching disabled and migrate the intended branch before deployment.
95
+
66
96
  ## Conflicting ids
67
97
 
68
98
  If `quickback.config.ts` already carries a real id for a resource and Cloudflare reports a different one for the same-named resource, `quickback deploy` prints both and stops:
@@ -173,6 +173,12 @@ get Postgres declarations; SQLite providers (`cloudflare-d1`,
173
173
  providers are refused with an error rather than written in the wrong
174
174
  dialect; no provider (or an unrecognized one) defaults to SQLite.
175
175
 
176
+ `quickback build` uses the same provider-to-dialect mapping when checking
177
+ managed columns, including with `--fix-schema`. An explicitly configured
178
+ unknown or MySQL provider stops the build before authored schema files are
179
+ changed. Omitting the database provider retains the SQLite default. Dialect
180
+ recognition does not add support for an unregistered database provider.
181
+
176
182
  ### Authored-Source Codemods
177
183
 
178
184
  ```bash
@@ -446,3 +452,38 @@ This can happen if your session token expired or if the API is temporarily unava
446
452
  quickback logout
447
453
  quickback login
448
454
  ```
455
+
456
+ ### Deploy a named target
457
+
458
+ ```bash
459
+ quickback deploy --env dev
460
+ quickback deploy --env prod --dry-run
461
+ ```
462
+
463
+ Named projects require a logical target from top-level `environments` or legacy
464
+ `providers.database.environments`. Quickback maps that key to the configured
465
+ `worker.env` and explicit Worker `name`; the Wrangler environment may differ
466
+ from the logical key. Only selected bindings participate in planning and D1
467
+ migrations. Unknown targets and duplicate placements reject before mutation.
468
+
469
+ Named D1/KV/Hyperdrive placeholder IDs must be provisioned and entered manually
470
+ in the target's `worker.bindings`, followed by `quickback build`. The CLI does
471
+ not overwrite global IDs for named targets. Postgres migrations and remote
472
+ Hyperdrive cache/target verification remain operator-owned. See
473
+ [Deploying](/start/deploy#named-deployment-targets).
474
+
475
+ ### Verify Neon migrations
476
+
477
+ ```bash
478
+ quickback canary dev --required
479
+ quickback canary prod --required --apply
480
+ ```
481
+
482
+ Canary uses the same logical environment mapping. `--required` fails instead
483
+ of skipping if credentials or branch configuration are missing; an unknown
484
+ named target or a non-Neon provider always fails. `--apply` rehearses on a
485
+ branch, then migrates the parent using the same selected database and migration
486
+ role. Local migration inventory changes abort parent apply. See
487
+ [Neon canaries](/platform/database/neon#required-migration-canaries) for role
488
+ selection, inventory-check limits and cleanup behavior. `quickback migrate`
489
+ continues to mean authored-source codemods, not database migration execution.