@m-kopa/launchpad-cli 0.63.0 → 0.65.0

package/CHANGELOG.md

@@ -6,7 +6,50 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html);
 pre-1.0 minor bumps may carry breaking changes per ADR 0005.
 
-## Unreleased
+## 0.65.0 - 2026-10-03
+
+### Added
+
+- `validate` and `plan` print a non-blocking warning for any container manifest: the platform's runtime switch may still be `off` for the app, in which case `launchpad deploy` returns HTTP 503 `container_runtime_off` (AIO-786).
+  A `runtime: aca` manifest gets a second warning — that value is reserved and currently ignored. Exit codes are unchanged; see `docs/concepts/containers.md` for the runtime gate, the `lite`-only container size, and the cold-start behaviour after idle.
+
+### Changed
+
+- Raise the production minimum CLI version to 0.64.0 through the governed policy workflow.
+- The `launchpad-deploy`, `launchpad-status` and `launchpad-deploy-status` skills keep a refused dispatch build on dispatch (AIO-756).
+  They name the `hidden build output is not supported` error and its fix, and they say that the Cloudflare account allows only 100 Pages projects.
+
+### Fixed
+
+- A first deploy with several hundred files no longer times out at `content_seeded` (AIO-738).
+  The platform now sends text files inside the git tree call, in chunks of at most 500 files or 8 MB, and checks every file's git SHA after the commit tree is built; if any SHA differs, it falls back to one blob per file.
+  Binary files still get their own blobs, created 8 at a time. A rate-limited blob or tree call retries, and the commit step has 10 minutes.
+- `launchpad destroy` now tears down an app whose provisioning failed at stage `pending` when main has no per-app Terraform.
+  It refuses with `tf_pr_open` while the app's Terraform PR is open, and with `dispatch_delivery_present` when a pre-Terraform app already has a dispatch delivery.
+- `launchpad deploy`'s apply-status polling (the automatic reconcile path for an access or origin change, e.g. switching `origin: dispatch` → `pages`) no longer goes quiet after a real `terraform apply` failure. Previously, once the bot recorded that failure and queued an automatic retry, every poll *before* the retry's PR opened fell through to a stale lookup and 404'd `no_apply_found` — which the CLI treats as "still settling" and retries. If the retry's regenerated Terraform happened to be byte-identical to what the failed attempt already merged (because the failed apply's file content lands on `main` even though the real infrastructure was never created), its PR carried an empty diff and never re-ran `terraform apply` at all, so the original failure could go unreported for as long as it took that empty retry to resolve (AIO-756). The bot now reports the already-known `failed` verdict on every poll in that window, so `launchpad deploy` exits non-zero with the failing stage named, instead of appearing to hang or (in the worst case) eventually reading as if nothing was wrong. Run `launchpad status <slug>` to confirm the current state after a reported failure.
+
+## 0.64.0 - 2026-09-25
+
+### Added
+
+- New `react+api` apps default to Workers dispatch too.
+  `launchpad init --type react+api` writes a v2 dispatch manifest with `functions/**` in the bundle; `--origin pages` still opts out.
+  A first `launchpad deploy` (or `launchpad migrate --origin dispatch`) of an unregistered React API app with a Pages-implied manifest converts it the same way static and React apps already convert.
+  `functions/` is compiled by the dispatch build, a v1 pages-target `d1_binding` or a single wrangler `d1_databases` entry becomes `spec.bindings.d1`, `production_env` values become plain-text env vars, and declared `env-file` secrets become `secret_text` env vars with a reminder to run `launchpad secrets push` once the first deploy is delivered.
+  The app stays on Pages with the reason printed when its wrangler config sets anything else (KV, R2, services, vars, Durable Objects and so on, named in the message), its functions have a root `_middleware` or root-level dynamic route that would claim every path, it ships a hand-written `_worker.js`, or a secret is platform-managed, targets another surface, or uses a name the platform sets.
+- `launchpad validate` refuses a v2 env var with the same name as `spec.bindings.d1`.
+- `launchpad secrets push` works for dispatch-origin apps.
+  The value goes to the app's Worker script in the dispatch namespace and is live immediately, so there is no redeploy prompt.
+  Pushing before the first deploy has been delivered stops with `dispatch_script_not_delivered` and writes nothing.
+  Fleet secret-set pushes reach dispatch members the same way.
+- `secrets template`, `push` and `status` read v2 manifests of either origin, taking each `spec.env_vars` entry of `type: secret_text` as a secret.
+  v2 dispatch manifests may now declare `secret_text` env vars.
+- Dispatch `react+api` apps can declare a D1 database as `spec.bindings.d1`, and `launchpad validate` accepts it.
+
+### Changed
+
+- Raise the production minimum CLI version to 0.63.0 through the governed policy workflow.
+  Older stable clients must run `launchpad update` before platform mutations.
 
 ## 0.63.0 - 2026-09-25