@m-kopa/launchpad-cli 0.54.0 → 0.55.0

package/CHANGELOG.md

@@ -8,6 +8,31 @@ pre-1.0 minor bumps may carry breaking changes per ADR 0005.
 
 ## Unreleased
 
+- Container commands now distinguish schema validity from runtime support before any network or filesystem mutation.
+  The first production runtime supports one local Dockerfile-backed container and rejects multi-container or registry-image manifests with a stable reason and field path.
+- Container generation now emits deterministic `container/wrangler.toml`, `container/worker/index.ts`, and `.github/workflows/deploy.yml` artifacts.
+  It refuses symlinks, non-regular Dockerfiles, multiple Dockerfiles, and custom platform artifact preimages.
+- Container deploys now use the same capability and filesystem checks as `validate`, `plan`, and `generate` before upload.
+
+- Platform operators can revoke a deploy-status capability immediately with `launchpad admin status-revoke <url>`, including capabilities on a non-production host selected through `LAUNCHPAD_STATUS_PAGE_HOST`.
+- Shareable deploy-status capability URLs now serve a noindex HTML timeline and a closed, free-text-free JSON schema with five-second ETag polling.
+- Apply PR descriptions now include a token-free pointer to `launchpad status <slug>` so reviewers know how to follow the deployment without exposing an ephemeral status capability.
+- Fixed Model A first deployments with Pages D1 bindings so provisioning creates or adopts the slug-named database before the initial content commit, pins that durable UUID into the exact build-root `wrangler.toml`, and binds the same UUID after Terraform creates the Pages project.
+  Provisioning now fails closed on unsafe or missing TOML targets and on post-Terraform UUID drift instead of allowing every initial Pages build to fail with a stale database UUID.
+- A manifest declaring a `pages` `d1_binding` with no `wrangler.toml` in its build root is now rejected with `400 bad_manifest`, naming the exact path expected, before the slug is claimed.
+  Previously this was accepted and then failed provisioning asynchronously at `content_seeded`, leaving the app in a failed lifecycle that needed `launchpad recover`.
+- `launchpad status` now includes the latest Pages deployment ID, time, failed stage, and bounded build-log excerpt for a failed provisioning lifecycle, while preserving exit code `0`.
+  The output labels this as latest evidence rather than claiming causality, reports why evidence is unavailable in JSON, and scrubs secret-shaped failed stages, excerpts, commit messages, and read errors.
+- `launchpad status` no longer contradicts itself when a read reconciles a failed record to live: it labels the lifecycle snapshot stale and suppresses the `launchpad recover` instruction instead of printing both.
+
+## 0.54.1 - 2026-07-29
+
+**Deleted application files now stay deleted after deployment.**
+
+- The legacy clone deploy path excludes tracked files that no longer exist in the working tree, allowing the server to derive their deletion from the complete upload.
+- The platform applies updates and proved app-owned deletions in one Git tree while preserving governance, workflow, ownership, Wrangler, Launchpad metadata, and out-of-boundary files.
+- The server uses exact managed-tree enumeration before absence can authorize deletion and returns a retryable failure when that proof is unavailable.
+
 ## 0.54.0 - 2026-07-19
 
 **Server-visible CLI compatibility, with dormant minimum-version enforcement.**