@webflow/webflow-cli 1.22.0-next.3 → 1.23.0

package/CHANGELOG.md

@@ -1,5 +1,34 @@
 # @webflow/webflow-cli
 
+## 1.23.0
+
+### Patch Changes
+
+- 32da176: Move file post processing for Devlink sync, from CLI to backend.
+
+## 1.22.0
+
+### Minor Changes
+
+- 75edc28: - `cloud deploy` no longer auto-routes to a site picker when the project is not initialized for Webflow Cloud. A new preflight phase resolves identity (site or workspace) before any backend call, preventing orphan Cloud apps when later steps fail.
+  - New scripting-friendly flags on `cloud deploy`: `-s, --site-id`, `-p, --project-id`, `-f, --framework`.
+  - Fix: `framework-detection` no longer overwrites unrelated `webflow.json` fields when auto-detecting a framework, and no longer throws on partial manifests that have a `cloud` block without a `framework` key — it falls back to `package.json` detection.
+
+### Patch Changes
+
+- b290822: `cloud deploy` now auto-detects the framework from `package.json` when `webflow.json` is missing or has no `cloud.framework`, instead of hard-failing. Detection uses the same builder registry that runs later in the build, and the resulting framework is written into a minimal `webflow.json` so subsequent deploys are stable. If no framework can be detected, the error now lists the supported options (astro / nextjs / vite). Also widens the cloud manifest schema with `.passthrough()` so CLI-managed fields like `project_id` survive the round-trip.
+- d97b310: - Fix `cloud deploy` writing complete framework metadata (`deployment_type` and `entrypoint_path`) into the bundle's `webflow.json`. Without this, Next.js / Remix deploys silently failed in the dashboard while the CLI reported success, because the deployer fell back to a generic `./index.js` entrypoint.
+  - `cloud init` now fetches site-attached scaffolds from GitHub (`Webflow-Examples/hello-world-*`) instead of bundling them in the CLI binary. No behavior change for end users beyond requiring network access during init.
+- 6dbf426: Fix the noisy `[DEP0040]` deprecation warning that appeared before every command's output when running on Node 22+. Other warnings continue to be shown as usual.
+- d56915a: Upgrade webflow-api to 3.3.4 to resolve elliptic audit finding.
+- ab60245: Exclude `dist` and `node_modules` when discovering Code Component declaration files.
+- e9dee8c: Fix `webflow library bundle` when the library `name` in `webflow.json` contains punctuation or other non-alphanumeric characters (except `-` and `_`). The bundler now derives a safe Module Federation identifier the same way component import names are normalized; symbol-only names fall back to `CodeLibrary`.
+- c9a430a: - Port the cosmic-builder `FrameworkBuilder` hierarchy into the CLI (`apps/webflow-cli/src/cloud/builder/`). The CLI's local build now shares the same framework support and behavior as the GitHub-import (cosmic) build path, so both producers ship equivalent tarballs to the cosmic deployer. Aligns with cosmic-builder v1.2.0's `webflow.json` contract (`entrypoint_path`, `deployment_type`). Fixes builds for frameworks whose dry-run entry isn't `./index.js` (Next.js → `./worker.js`, Astro 6 → `./entry.mjs`, Vite → `./src/worker.ts`) — includes the Next.js deploy fix for CLD-1619.
+  - `handleWranglerJson` is now the single owner of `wrangler.json` during the build; framework `prepareConfig()` implementations no longer redundantly copy the template after user bindings have been merged, so KV / R2 / D1 bindings now reliably appear in the local dry-run output.
+  - `webflow.json` is now copied into the deploy tarball, so the cosmic deployer can identify the framework for Astro / Vite tarballs (previously bailed with "could not find webflow.json in extracted output").
+  - Internal: introduces `logStageBanner(emoji, label)` for consistent build-stage output. Removes the experimental Remix framework builder (was never wired up to scaffolds in production).
+- 5853814: docs: add Forms commands section to README for v1.21.0
+
 ## 1.21.0
 
 ### Minor Changes