Sitecore/content-sdk @sitecore-content-sdk/cli@2.3.0

on GitHub

Minor Changes

• minor @sitecore-content-sdk/content dependency update:

  • Pass the page language to Sitecore Forms to support new multilingual form versions. (fa0496c)
  • Add metadata and Open Graph tags to the NextJs scaffolding templates (914f94a)
  • [experimental] Add a global env switch for experimental features.

  Experimental feature status now treats the app-level CSDK_GLOBAL_EXPERIMENTAL_FEATURES_ENABLED as a global enable switch. When the global switch is off, feature status falls back to individual feature env vars. The shared experimental helpers expose the global env var constant (CSDK_GLOBAL_EXPERIMENTAL_FEATURES_FLAG) and helper, and starter env examples document how to enable experimental features during development. (c9c8d1c)

  • [experimental] Add experimental features visibility API shared across frameworks. Types/utils live in @sitecore-content-sdk/content; each framework package owns its experimental.json catalog. Next.js and Angular expose editing-secret protected endpoints, wired in all Next.js templates and the Angular server. (b4fad5b)

  • Treat Layout Service isContentResolved as datasource validity in withDatasourceCheck()

  • ComponentRendering now includes optional isContentResolved from the layout rendered JSON

  • When isContentResolved is false, withDatasourceCheck() uses the existing missing-datasource fallback

  • When the property is omitted or true, existing behavior is unchanged (afdfd19)

    • Use CSDK_PUBLIC_DEFAULT_SITE_NAME variable instead of CSDK_PUBLIC_SITECORE_DEFAULT_SITE, aligning names across frameworks
    • When upgrading from your pre-release Angular app, please ensure you use CSDK_PUBLIC_DEFAULT_SITE_NAME and CSDK_PUBLIC_DEFAULT_LANGUAGE across your deployments
    • Check the updated env.example in the latest available Angular sample for the up-to-date list of available environnment variables (ccaa42f)
    • Add support of llms txt for all next apps through api routes. (d2b0a9f)

Patch Changes

• [cli] Fix debug logs not being written by sitecore-tools when DEBUG is set in an .env file of an app running inside the content-sdk monorepo. The debug scopes are now enabled through @sitecore-content-sdk/core, so they are applied to the same 'debug' instance the SDK packages log through instead of a separate copy of the module the CLI resolves on its own. (b14e738)