@quickback-dev/cli 0.60.2 → 0.60.3

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/dist/index.js CHANGED
@@ -10,7 +10,7 @@
10
10
  */
11
11
  import pc from "picocolors";
12
12
  // Version injected at build time by scripts/inject-version.ts
13
- const CLI_VERSION = "0.60.2";
13
+ const CLI_VERSION = "0.60.3";
14
14
  function getPackageVersion() {
15
15
  return CLI_VERSION;
16
16
  }
@@ -4,7 +4,7 @@ Build a backend in [Quickback Start](https://start.quickback.dev), get a green c
4
4
 
5
5
  This page covers the browser flow. For local projects, or anything the browser flow doesn't support yet, use [`quickback deploy`](/start/deploy) — the CLI covers every resource type and is always available.
6
6
 
7
- > Browser deployment is rolling out. The hosted deploy service ships fail-closed behind a kill switch while the final authentication work lands; if the Deploy card doesn't appear in Start, your session isn't in the rollout yet. `quickback deploy` works for everyone today.
7
+ > Browser deployment is new. The hosted deploy service sits behind a kill switch, and provisioning is rate-limited to 5 deploys per minute per user — enough to stop a runaway retry loop, not something a normal deploy will ever hit. `quickback deploy` works for everyone today.
8
8
 
9
9
 
10
10
  ## Browser vs CLI
@@ -90,7 +90,8 @@ The deploy card is the whole connection UI: it reports the state of your Cloudfl
90
90
  | "This Cloudflare connection can't …" | The grant is missing a permission a deploy needs (an older connection, or a scope your OAuth client didn't allow) | **Reconnect Cloudflare** to grant the rest |
91
91
  | "This Cloudflare login isn't a member of any account" | The identity you connected belongs to no Cloudflare account | Create or join an account in the Cloudflare dashboard, then reconnect |
92
92
  | "Couldn't reach the deploy service…" | Transient failure talking to Quickback or Cloudflare | **Try again** |
93
- | "Browser deploys are still rolling out" | Your session isn't in the rollout | Use [`quickback deploy`](/start/deploy) |
93
+ | "Browser deploys aren't fully configured on the server yet" | A deploy-service misconfiguration, not anything on your side | Use [`quickback deploy`](/start/deploy) for now |
94
+ | "Too many deploys in a minute" | More than 5 provisions in a minute on one account | Wait for the `Retry-After` window and click Deploy again |
94
95
 
95
96
  Deploy is disabled while a reconnect is pending, so a deploy never starts on a connection that can't finish it. If a connection dies *during* a deploy, the failure comes back as a reconnect prompt rather than a raw error — the deploy is safe to re-run after reconnecting, because provisioning adopts and migrations apply once.
96
97
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@quickback-dev/cli",
3
- "version": "0.60.2",
3
+ "version": "0.60.3",
4
4
  "description": "CLI for Quickback — define your backend in TypeScript, compile to a fully wired Cloudflare Worker (or Bun / Node) with auth, database, migrations, security, CMS, and Account UI.",
5
5
  "author": "Kardoe Incorporated <paul@kardoe.com>",
6
6
  "license": "MIT",
@@ -4,7 +4,7 @@ Build a backend in [Quickback Start](https://start.quickback.dev), get a green c
4
4
 
5
5
  This page covers the browser flow. For local projects, or anything the browser flow doesn't support yet, use [`quickback deploy`](/start/deploy) — the CLI covers every resource type and is always available.
6
6
 
7
- > Browser deployment is rolling out. The hosted deploy service ships fail-closed behind a kill switch while the final authentication work lands; if the Deploy card doesn't appear in Start, your session isn't in the rollout yet. `quickback deploy` works for everyone today.
7
+ > Browser deployment is new. The hosted deploy service sits behind a kill switch, and provisioning is rate-limited to 5 deploys per minute per user — enough to stop a runaway retry loop, not something a normal deploy will ever hit. `quickback deploy` works for everyone today.
8
8
 
9
9
 
10
10
  ## Browser vs CLI
@@ -90,7 +90,8 @@ The deploy card is the whole connection UI: it reports the state of your Cloudfl
90
90
  | "This Cloudflare connection can't …" | The grant is missing a permission a deploy needs (an older connection, or a scope your OAuth client didn't allow) | **Reconnect Cloudflare** to grant the rest |
91
91
  | "This Cloudflare login isn't a member of any account" | The identity you connected belongs to no Cloudflare account | Create or join an account in the Cloudflare dashboard, then reconnect |
92
92
  | "Couldn't reach the deploy service…" | Transient failure talking to Quickback or Cloudflare | **Try again** |
93
- | "Browser deploys are still rolling out" | Your session isn't in the rollout | Use [`quickback deploy`](/start/deploy) |
93
+ | "Browser deploys aren't fully configured on the server yet" | A deploy-service misconfiguration, not anything on your side | Use [`quickback deploy`](/start/deploy) for now |
94
+ | "Too many deploys in a minute" | More than 5 provisions in a minute on one account | Wait for the `Retry-After` window and click Deploy again |
94
95
 
95
96
  Deploy is disabled while a reconnect is pending, so a deploy never starts on a connection that can't finish it. If a connection dies *during* a deploy, the failure comes back as a reconnect prompt rather than a raw error — the deploy is safe to re-run after reconnecting, because provisioning adopts and migrations apply once.
96
97