fix(deps): update dependency @frontify/frontify-cli to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@frontify/frontify-cli (source)	^5.9.4 → ^6.0.0

---

Release Notes

Frontify/brand-sdk (@​frontify/frontify-cli)

v6.2.1

Compare Source

Patch Changes

• #​1584 bbe3339 Thanks @​ragi96! - chore(deps): bump dependencies in scaffolded content-block templates

  Newly scaffolded content-block-css, content-block-css-modules, and content-block-tailwind projects pin updated @frontify/app-bridge, @frontify/guideline-blocks-settings, and @frontify/frontify-cli versions, with @frontify/guideline-blocks-settings now declared as a runtime dependency.

• #​1586 2575dba Thanks @​jorgsowa! - chore(deps): bump template dependencies

  Updated dependencies in platform-app and content-block-tailwind scaffolded templates, including newer versions of @frontify/app-bridge-app, @frontify/fondue, @frontify/platform-app, @frontify/frontify-cli, @types/react, @types/react-dom, and other dev dependencies.

v6.2.0

Compare Source

Minor Changes

• #​1578 a2b5431 Thanks @​ragi96! - feat(serve): include the block manifest in the /_entrypoint dev-server response

  The block development server now reads manifest.json from the project root on each /_entrypoint request and returns its parsed content under a manifest field, so the host can pick up live manifest changes without restarting frontify-cli serve. If manifest.json is missing or unparseable, the field is omitted and a warning is logged.

  GET http://localhost:5600/_entrypoint
  {
      "url": "http://localhost:5600/src/index.ts",
      "entryFilePath": "src/index.ts",
      "port": 5600,
      "version": "6.1.0",
      "dependencies": { "@​frontify/app-bridge": "^4.0.0", "react": "^18.3.1" },
      "manifest": { "appId": "abc123…" }
  }

Patch Changes

• #​1583 866c444 Thanks @​ragi96! - chore(deps): bump fastify to ^5.8.5 and vite to ^8.0.10

• #​1581 11b6c03 Thanks @​renovate! - chore(deps): bump @frontify/guideline-blocks-settings to 2.1.10 in scaffolded content-block templates

v6.1.0

Compare Source

Minor Changes

• #​1564 ca53cc3 Thanks @​ragi96! - feat(CLI): add verify-manifest command to validate the local manifest.json against the Frontify Marketplace before deploying

  Example usage:

  frontify-cli verify-manifest
  frontify-cli verify-manifest --app-type content-block
  frontify-cli verify-manifest --app-type content-block --instance my-instance.frontify.com --token <accessToken>

Patch Changes

• #​1566 3889cea Thanks @​ragi96! - chore(Deps): bumping some devDependencies

v6.0.4

Compare Source

Patch Changes

• #​1560 112553a Thanks @​ragi96! - fix(cli): repair content-block templates

  • Replace removed IconEnum import with string icon name in settings.ts
  • Pin @udecode/plate-common to 36.5.9 via overrides/resolutions to avoid the deprecated 42.0.0 shim that breaks Rollup builds
  • Pin zustand to 4.5.7 so blocks don't pick up zustand@5 (incompatible API with @udecode/zustood / zustand-x, causing TypeError: createState is not a function when the block loads in the web-app)
  • Use arbitrary-value color classes in the Tailwind template so the example renders correctly under the Frontify Tailwind preset (which replaces the default blue/green/red palette)

• #​1561 830efe3 Thanks @​ragi96! - chore(cli): bump content-block template dev toolchain

  • eslint 8 → 10 (flat config); @frontify/eslint-config-react 0.17 → 1.0.15
  • typescript 5 → 6
  • tailwindcss 3.4.3 → 3.4.19, autoprefixer 10.4.22 → 10.5.0, explicit postcss dep (tailwind template)
  • Replace deprecated tailwindcss/tailwind.css side-effect import with a local src/style.css using @tailwind directives
  • Pin @frontify/guideline-blocks-settings to exact 2.1.8
  • Migrate .eslintrc.cjs → eslint.config.mjs (flat config)

v6.0.3

Compare Source

Patch Changes

• #​1555 f12d05b Thanks @​floriangaechter! - fix(cli): correct guideline-blocks-settings version in templates

v6.0.2

Compare Source

Patch Changes

• #​1551 4a51843 Thanks @​jeremyzahner! - fix(cli): resolve dependency versions from node_modules instead of package.json specifiers

  The development server and platform app compiler were reading React and App Bridge versions directly from the consumer's package.json dependencies field. This broke when using pnpm workspaces with the catalog: or workspace:* protocols, since those specifiers were passed as-is to the bundler instead of actual version numbers.

  Version resolution now uses Node's built-in findPackageJSON (available since Node 22.14.0, matching the CLI's >=22 engine requirement) to directly locate each package's package.json in node_modules. A fallback to the consumer's package.json is preserved for environments where node_modules is not yet populated, and checks devDependencies and peerDependencies in addition to dependencies.

v6.0.1

Compare Source

Patch Changes

• #​1549 2317a2a Thanks @​ragi96! - fix(cli): default appType to content-block in deploy command

  When neither the --app-type CLI option nor the manifest.json appType field is set, the deploy command now falls back to 'content-block' instead of remaining undefined. This prevents deployment failures for projects that omit the appType from their manifest.

v6.0.0

Compare Source

Major Changes

• #​1546 dec69a9 Thanks @​ragi96! - feat: support React 19

  The CLI now supports React 19 to stay up-to-date with the React ecosystem and provide better performance and modern features.
  Consumers can from now on update their block / theme to React 19.

• #​1546 dec69a9 Thanks @​ragi96! - chore: update required node to 22

  The minimum required Node.js version has been bumped from 18 to 22.
  Node.js 18 is reaching its end-of-life. Node 22 is the current Active LTS release.
  Consumers must update their local development environments and CI/CD pipelines to use Node.js version 22 or higher.

• #​1546 dec69a9 Thanks @​ragi96! - feat: remove deprecated block and theme subcommands

  The following deprecated commands have been removed:

  • block serve / theme serve → use serve instead
  • block deploy / theme deploy → use deploy instead
  • block create / theme create → use create instead

• #​1546 dec69a9 Thanks @​ragi96! - feat: build blocks / themes as ESM packages

  Custom blocks and themes are now compiled and output as ECMAScript Modules (ESM) instead of relying on global window variables.
  ESM is the modern standard for JavaScript, offering better interoperability, tree-shaking and compatibility with modern bundlers.
  Consumers don't need to do anything to migrate to ESM, but they should be aware of the changes.

Minor Changes

• #​1546 dec69a9 Thanks @​ragi96! - feat: add publish command for publishing apps to the Frontify Marketplace

  Publish your app directly from the CLI using frontify-cli publish.

Usage

```bash

# Publish with release notes (required)
frontify-cli publish --release-notes="Initial release"

# Publish with community availability (default: PRIVATE)
frontify-cli publish --release-notes="Bug fixes" --availability=COMMUNITY

# Publish using explicit credentials instead of stored login
frontify-cli publish --release-notes="New feature" --token=<access-token> --instance=<instance-url>
```

Patch Changes

• #​1546 dec69a9 Thanks @​ragi96! - fix: resolve all ESLint warnings across the CLI package

  • Add typed interfaces (LoginOptions, ServeOptions, DeployOptions) for CLI action callbacks to eliminate unsafe any access on command options
  • Cast prompts() return values to proper types instead of implicit any destructuring
  • Handle floating promises in login.ts and platformAppDevelopmentServer.ts with .catch() instead of fire-and-forget
  • Replace @ts-expect-error workarounds in promiseExec.ts with proper String() coercion
  • Refactor reactiveJson.ts to use typed JSON.parse, Record-based proxy handler, and instanceof/in checks instead of as any casts
  • Replace as any casts in vitePlugins.ts with Record<string, unknown> for rolldownOptions access
  • Add local Archive interface in zip.ts to properly type the untyped archiver module
  • Use keyof typeof cast in gitignoreTemplate.ts for safe object indexing
  • Type dynamic import() results and JSON.parse calls in test files
  • Remove unused eslint-disable directives

• #​1546 dec69a9 Thanks @​ragi96! - fix: CLI bug fixes and cleanup

  • Fix typo sucess → success in HTTP error response type
  • Fix hardcoded port in OAuth redirect URI (now uses the configured --port value)
  • Fix missing / separator in deploy build file ignore glob pattern
  • Remove node-fetch dependency in favor of native fetch (Node >=22)
  • Handle full 2xx status range in HTTP client instead of only 200
  • Eliminate duplicated deploy command branches in CLI entry point
  • Reduce cognitive complexity in deploy command by extracting helper functions

• #​1546 dec69a9 Thanks @​ragi96! - chore: updated the block templates

• #​1546 dec69a9 Thanks @​ragi96! - chore: remove nock dependency, use vitest mocks instead

• #​1546 dec69a9 Thanks @​ragi96! - core(Deps): Bump esbuild and vite dependencies

• #​1546 dec69a9 Thanks @​ragi96! - fix: add missing CSS and JS minification to platform-app compiler

  • Add cssFileName: 'style' to the settings lib build
  • Add minify: 'terser' for JS minification
  • Set explicit mode: 'production' on both builds

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.