Skip to content

[csdk] latest release - #622

Open
jss-release-github-app[bot] wants to merge 1 commit into
devfrom
changeset-release/dev
Open

[csdk] latest release#622
jss-release-github-app[bot] wants to merge 1 commit into
devfrom
changeset-release/dev

Conversation

@jss-release-github-app

@jss-release-github-app jss-release-github-app Bot commented Sep 10, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to dev, this PR will be updated.

Releases

@sitecore-content-sdk/angular@1.1.0

Minor Changes

  • [angular] llms.txt Support (c7801c3)

    Added createLlmsTxtMiddleware({ client, sites }), an Express handler serving the llms.txt content managed via SitecoreAI for the site resolved by host name. The Angular template mounts it at /llms.txt.

  • [angular] Metadata, Open Graph and Schema.org & JSON-LD Support (c7801c3)

    • @sitecore-content-sdk/content: resolvePageMetadataFields (with PageMetadataRouteFields / ResolvedPageMetadataFields) moved from @sitecore-content-sdk/nextjs to @sitecore-content-sdk/content/layout, so every framework shares the same field-to-tag rules. @sitecore-content-sdk/nextjs keeps re-exporting PageMetadataRouteFields.
    • @sitecore-content-sdk/angular: added PageMetadataService + <sc-page-meta-tags [route]> (<title>, metadata and Open Graph <meta> tags via Angular's Title/Meta services) and JsonLdSchemaService + <sc-json-ld-schema [page]> (a single <script type="application/ld+json"> in <head>, normal mode only). Re-exported the PageMetadataFields, MetadataFields, OpenGraphFields, OpenGraphImageField(Value) and PageMetadataRouteFields types.
    • Angular template: LayoutComponent renders both components; RouteFields extends PageMetadataFields.

  • Add sitecore-tools project experimental list to show the experimental features available in the current Content SDK app. (e1d0156)
    The command reads the app's framework package (@sitecore-content-sdk/nextjs or @sitecore-content-sdk/angular) and prints each feature with its enabled status. Framework packages now export experimentalFeaturesCatalog from their /experimental entry.

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

    • [angular] Metadata, Open Graph and Schema.org & JSON-LD Support

    • @sitecore-content-sdk/content: resolvePageMetadataFields (with PageMetadataRouteFields / ResolvedPageMetadataFields) moved from @sitecore-content-sdk/nextjs to @sitecore-content-sdk/content/layout, so every framework shares the same field-to-tag rules. @sitecore-content-sdk/nextjs keeps re-exporting PageMetadataRouteFields.

    • @sitecore-content-sdk/angular: added PageMetadataService + <sc-page-meta-tags [route]> (<title>, metadata and Open Graph <meta> tags via Angular's Title/Meta services) and JsonLdSchemaService + <sc-json-ld-schema [page]> (a single <script type="application/ld+json"> in <head>, normal mode only). Re-exported the PageMetadataFields, MetadataFields, OpenGraphFields, OpenGraphImageField(Value) and PageMetadataRouteFields types.

    • Angular template: LayoutComponent renders both components; RouteFields extends PageMetadataFields. (c7801c3)

      • Schema.org & JSON-LD Support (b858df1)

Patch Changes

  • Fixed next dev --webpack / next build --webpack failing with UnhandledSchemeError for (ab9e875)
    node:events when the generated .sitecore/import-map.ts imported combineImportEntries.

    content/tools stays the browser-safe entry for that helper. Pure component-map helpers now live
    apart from glob, and the Node-only prepareComponentsForMap / buildComponentMapContent
    helpers (which depend on path) are exported from content/node-tools.

  • Sitecore webhook revalidation no longer invalidates dictionary data for every configured site on (df0ab91)
    every call — only an actual Dictionary entry update revalidates its own site's dictionary tag.

    createSitecoreRevalidateRouteHandler (Next.js) and createSitecoreRevalidateMiddleware (Angular)
    previously appended a sc:dict:<site>:<locale> tag for every site in sites on every webhook
    call, regardless of what the payload actually changed. Because dictionary data is shared across
    nearly every page, this meant any unrelated content update - or even a call with no dictionary
    changes at all - revalidated every page for that site and locale, defeating the benefit of
    targeted, on-demand revalidation.

  • sc:item tags no longer carry a version segment (sc:item:<id>:<locale>), so cache writes and (bdfa673)
    webhook revalidation always agree.
    Item cache tags could previously include a specific published version (sc:item:<id>:<locale>:v<N>)
    when the layout response reported itemVersion, but webhook-driven revalidation always targets
    sc:item:<id>:<locale>:latest. The mismatch meant those page cache entries were silently unreachable by revalidateTag and only went stale on cache TTL expiry.

  • <sc-placeholder-metadata> now renders with display: contents, so components inside a placeholder lay out correctly in flex and grid containers in editing mode. (0356f0f)

    The wrapper element that emits the Sitecore chrome markers had no styles and therefore rendered as display: inline. Inside a flex or grid parent, the wrapper became the flex/grid item instead of the component, so the component's own layout styles (e.g. display: block, flex sizing) no longer applied to the parent layout and the page looked different in the Pages editor than in the published site.

  • sc:item tags now always use hyphenated lowercase GUIDs (sc:item:<hyphenated-id>:<locale>:latest), so cache writes and webhook revalidation always agree. (330793b)

    Experience Edge publish payloads send unhyphenated item IDs (xxxxxxxxx). Cached pages already tag content with hyphenated lowercase GUIDs (sc:item:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:...). Because Next.js / loader cache tags are compared as exact strings, those invalidation tags missed and published updates could stay stale.

@sitecore-content-sdk/cli@2.4.0

Minor Changes

  • Add sitecore-tools project experimental list to show the experimental features available in the current Content SDK app. (e1d0156)
    The command reads the app's framework package (@sitecore-content-sdk/nextjs or @sitecore-content-sdk/angular) and prints each feature with its enabled status. Framework packages now export experimentalFeaturesCatalog from their /experimental entry.

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

    • [angular] Metadata, Open Graph and Schema.org & JSON-LD Support

    • @sitecore-content-sdk/content: resolvePageMetadataFields (with PageMetadataRouteFields / ResolvedPageMetadataFields) moved from @sitecore-content-sdk/nextjs to @sitecore-content-sdk/content/layout, so every framework shares the same field-to-tag rules. @sitecore-content-sdk/nextjs keeps re-exporting PageMetadataRouteFields.

    • @sitecore-content-sdk/angular: added PageMetadataService + <sc-page-meta-tags [route]> (<title>, metadata and Open Graph <meta> tags via Angular's Title/Meta services) and JsonLdSchemaService + <sc-json-ld-schema [page]> (a single <script type="application/ld+json"> in <head>, normal mode only). Re-exported the PageMetadataFields, MetadataFields, OpenGraphFields, OpenGraphImageField(Value) and PageMetadataRouteFields types.

    • Angular template: LayoutComponent renders both components; RouteFields extends PageMetadataFields. (c7801c3)

      • Schema.org & JSON-LD Support (b858df1)

@sitecore-content-sdk/content@2.4.0

Minor Changes

  • [angular] Metadata, Open Graph and Schema.org & JSON-LD Support (c7801c3)

    • @sitecore-content-sdk/content: resolvePageMetadataFields (with PageMetadataRouteFields / ResolvedPageMetadataFields) moved from @sitecore-content-sdk/nextjs to @sitecore-content-sdk/content/layout, so every framework shares the same field-to-tag rules. @sitecore-content-sdk/nextjs keeps re-exporting PageMetadataRouteFields.
    • @sitecore-content-sdk/angular: added PageMetadataService + <sc-page-meta-tags [route]> (<title>, metadata and Open Graph <meta> tags via Angular's Title/Meta services) and JsonLdSchemaService + <sc-json-ld-schema [page]> (a single <script type="application/ld+json"> in <head>, normal mode only). Re-exported the PageMetadataFields, MetadataFields, OpenGraphFields, OpenGraphImageField(Value) and PageMetadataRouteFields types.
    • Angular template: LayoutComponent renders both components; RouteFields extends PageMetadataFields.

  • Schema.org & JSON-LD Support (b858df1)

Patch Changes

  • Fixed next dev --webpack / next build --webpack failing with UnhandledSchemeError for (ab9e875)
    node:events when the generated .sitecore/import-map.ts imported combineImportEntries.

    content/tools stays the browser-safe entry for that helper. Pure component-map helpers now live
    apart from glob, and the Node-only prepareComponentsForMap / buildComponentMapContent
    helpers (which depend on path) are exported from content/node-tools.

  • Avoid throwing errors in scClient calls when context ID in browser is missing. (5184ea7)

    • Replaces the GraphQL client used by scClient with no-op fallback in browser context, when public content ID is missing, preventing getPage(), getDictionary() and other GraphQL-bound method from throwing.
    • Adds edgeInitialized to scClient to indicate the status of Sitecore Edge connectivity. false in browser when public Edge context ID is missing.
    • Adds a guard into getHeadLinks() call to return empty results when both server and client context IDs are missing, instead of throwing an error.

  • Send the Sitecore Context ID for Forms in the x-sitecore-contextid header instead of the query string, and use the public/client context ID for stylesheet <link> URLs so the server context ID is not rendered in page markup. (a8a17de)

@sitecore-content-sdk/nextjs@2.5.0

Minor Changes

  • Add sitecore-tools project experimental list to show the experimental features available in the current Content SDK app. (e1d0156)
    The command reads the app's framework package (@sitecore-content-sdk/nextjs or @sitecore-content-sdk/angular) and prints each feature with its enabled status. Framework packages now export experimentalFeaturesCatalog from their /experimental entry.

  • Schema.org & JSON-LD Support (b858df1)

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

    • [angular] Metadata, Open Graph and Schema.org & JSON-LD Support

    • @sitecore-content-sdk/content: resolvePageMetadataFields (with PageMetadataRouteFields / ResolvedPageMetadataFields) moved from @sitecore-content-sdk/nextjs to @sitecore-content-sdk/content/layout, so every framework shares the same field-to-tag rules. @sitecore-content-sdk/nextjs keeps re-exporting PageMetadataRouteFields.

    • @sitecore-content-sdk/angular: added PageMetadataService + <sc-page-meta-tags [route]> (<title>, metadata and Open Graph <meta> tags via Angular's Title/Meta services) and JsonLdSchemaService + <sc-json-ld-schema [page]> (a single <script type="application/ld+json"> in <head>, normal mode only). Re-exported the PageMetadataFields, MetadataFields, OpenGraphFields, OpenGraphImageField(Value) and PageMetadataRouteFields types.

    • Angular template: LayoutComponent renders both components; RouteFields extends PageMetadataFields. (c7801c3)

      • Schema.org & JSON-LD Support (b858df1)

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

    • Schema.org & JSON-LD Support (b858df1)

Patch Changes

  • [angular] Metadata, Open Graph and Schema.org & JSON-LD Support (c7801c3)

    • @sitecore-content-sdk/content: resolvePageMetadataFields (with PageMetadataRouteFields / ResolvedPageMetadataFields) moved from @sitecore-content-sdk/nextjs to @sitecore-content-sdk/content/layout, so every framework shares the same field-to-tag rules. @sitecore-content-sdk/nextjs keeps re-exporting PageMetadataRouteFields.
    • @sitecore-content-sdk/angular: added PageMetadataService + <sc-page-meta-tags [route]> (<title>, metadata and Open Graph <meta> tags via Angular's Title/Meta services) and JsonLdSchemaService + <sc-json-ld-schema [page]> (a single <script type="application/ld+json"> in <head>, normal mode only). Re-exported the PageMetadataFields, MetadataFields, OpenGraphFields, OpenGraphImageField(Value) and PageMetadataRouteFields types.
    • Angular template: LayoutComponent renders both components; RouteFields extends PageMetadataFields.

  • Fixed next dev --webpack / next build --webpack failing with UnhandledSchemeError for (ab9e875)
    node:events when the generated .sitecore/import-map.ts imported combineImportEntries.

    content/tools stays the browser-safe entry for that helper. Pure component-map helpers now live
    apart from glob, and the Node-only prepareComponentsForMap / buildComponentMapContent
    helpers (which depend on path) are exported from content/node-tools.

  • Sitecore webhook revalidation no longer invalidates dictionary data for every configured site on (df0ab91)
    every call — only an actual Dictionary entry update revalidates its own site's dictionary tag.

    createSitecoreRevalidateRouteHandler (Next.js) and createSitecoreRevalidateMiddleware (Angular)
    previously appended a sc:dict:<site>:<locale> tag for every site in sites on every webhook
    call, regardless of what the payload actually changed. Because dictionary data is shared across
    nearly every page, this meant any unrelated content update - or even a call with no dictionary
    changes at all - revalidated every page for that site and locale, defeating the benefit of
    targeted, on-demand revalidation.

  • MultisiteProxy now resolves the site from the unprefixed site query string parameter only for draft mode App Router requests, so third-party requests containing ?site=... no longer override the resolved site or overwrite the sc_site cookie. (d6b8d75)

    If you need to force the site via query string, use the sc_site parameter (the supported one) instead of site. Site resolution in editing is unaffected.

  • sc:item tags no longer carry a version segment (sc:item:<id>:<locale>), so cache writes and (bdfa673)
    webhook revalidation always agree.
    Item cache tags could previously include a specific published version (sc:item:<id>:<locale>:v<N>)
    when the layout response reported itemVersion, but webhook-driven revalidation always targets
    sc:item:<id>:<locale>:latest. The mismatch meant those page cache entries were silently unreachable by revalidateTag and only went stale on cache TTL expiry.

  • sc:item tags now always use hyphenated lowercase GUIDs (sc:item:<hyphenated-id>:<locale>:latest), so cache writes and webhook revalidation always agree. (330793b)

    Experience Edge publish payloads send unhyphenated item IDs (xxxxxxxxx). Cached pages already tag content with hyphenated lowercase GUIDs (sc:item:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx:...). Because Next.js / loader cache tags are compared as exact strings, those invalidation tags missed and published updates could stay stale.

@sitecore-content-sdk/react@2.5.0

Minor Changes

  • Schema.org & JSON-LD Support (b858df1)

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

    • [angular] Metadata, Open Graph and Schema.org & JSON-LD Support

    • @sitecore-content-sdk/content: resolvePageMetadataFields (with PageMetadataRouteFields / ResolvedPageMetadataFields) moved from @sitecore-content-sdk/nextjs to @sitecore-content-sdk/content/layout, so every framework shares the same field-to-tag rules. @sitecore-content-sdk/nextjs keeps re-exporting PageMetadataRouteFields.

    • @sitecore-content-sdk/angular: added PageMetadataService + <sc-page-meta-tags [route]> (<title>, metadata and Open Graph <meta> tags via Angular's Title/Meta services) and JsonLdSchemaService + <sc-json-ld-schema [page]> (a single <script type="application/ld+json"> in <head>, normal mode only). Re-exported the PageMetadataFields, MetadataFields, OpenGraphFields, OpenGraphImageField(Value) and PageMetadataRouteFields types.

    • Angular template: LayoutComponent renders both components; RouteFields extends PageMetadataFields. (c7801c3)

      • Schema.org & JSON-LD Support (b858df1)

create-content-sdk-app@2.4.1

Patch Changes

  • [angular] llms.txt Support (c7801c3)

    Added createLlmsTxtMiddleware({ client, sites }), an Express handler serving the llms.txt content managed via SitecoreAI for the site resolved by host name. The Angular template mounts it at /llms.txt.

  • [angular] Metadata, Open Graph and Schema.org & JSON-LD Support (c7801c3)

    • @sitecore-content-sdk/content: resolvePageMetadataFields (with PageMetadataRouteFields / ResolvedPageMetadataFields) moved from @sitecore-content-sdk/nextjs to @sitecore-content-sdk/content/layout, so every framework shares the same field-to-tag rules. @sitecore-content-sdk/nextjs keeps re-exporting PageMetadataRouteFields.
    • @sitecore-content-sdk/angular: added PageMetadataService + <sc-page-meta-tags [route]> (<title>, metadata and Open Graph <meta> tags via Angular's Title/Meta services) and JsonLdSchemaService + <sc-json-ld-schema [page]> (a single <script type="application/ld+json"> in <head>, normal mode only). Re-exported the PageMetadataFields, MetadataFields, OpenGraphFields, OpenGraphImageField(Value) and PageMetadataRouteFields types.
    • Angular template: LayoutComponent renders both components; RouteFields extends PageMetadataFields.

  • Sitecore webhook revalidation no longer invalidates dictionary data for every configured site on (df0ab91)
    every call — only an actual Dictionary entry update revalidates its own site's dictionary tag.

    createSitecoreRevalidateRouteHandler (Next.js) and createSitecoreRevalidateMiddleware (Angular)
    previously appended a sc:dict:<site>:<locale> tag for every site in sites on every webhook
    call, regardless of what the payload actually changed. Because dictionary data is shared across
    nearly every page, this meant any unrelated content update - or even a call with no dictionary
    changes at all - revalidated every page for that site and locale, defeating the benefit of
    targeted, on-demand revalidation.

  • Schema.org & JSON-LD Support (b858df1)

  • sc:item tags no longer carry a version segment (sc:item:<id>:<locale>), so cache writes and (bdfa673)
    webhook revalidation always agree.
    Item cache tags could previously include a specific published version (sc:item:<id>:<locale>:v<N>)
    when the layout response reported itemVersion, but webhook-driven revalidation always targets
    sc:item:<id>:<locale>:latest. The mismatch meant those page cache entries were silently unreachable by revalidateTag and only went stale on cache TTL expiry.

  • Add @sitecore-content-sdk/personalize to the Next.js Pages Router template dependencies. Yarn does not install missing peers, so a Pages Router app built with Yarn could not resolve the package and omitted it from .sitecore/metadata.json. (16c65a2)

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

    • [angular] llms.txt Support

    Added createLlmsTxtMiddleware({ client, sites }), an Express handler serving the llms.txt content managed via SitecoreAI for the site resolved by host name. The Angular template mounts it at /llms.txt. (c7801c3)

    • [angular] Metadata, Open Graph and Schema.org & JSON-LD Support

    • @sitecore-content-sdk/content: resolvePageMetadataFields (with PageMetadataRouteFields / ResolvedPageMetadataFields) moved from @sitecore-content-sdk/nextjs to @sitecore-content-sdk/content/layout, so every framework shares the same field-to-tag rules. @sitecore-content-sdk/nextjs keeps re-exporting PageMetadataRouteFields.

    • @sitecore-content-sdk/angular: added PageMetadataService + <sc-page-meta-tags [route]> (<title>, metadata and Open Graph <meta> tags via Angular's Title/Meta services) and JsonLdSchemaService + <sc-json-ld-schema [page]> (a single <script type="application/ld+json"> in <head>, normal mode only). Re-exported the PageMetadataFields, MetadataFields, OpenGraphFields, OpenGraphImageField(Value) and PageMetadataRouteFields types.

    • Angular template: LayoutComponent renders both components; RouteFields extends PageMetadataFields. (c7801c3)

      • Add sitecore-tools project experimental list to show the experimental features available in the current Content SDK app.
        The command reads the app's framework package (@sitecore-content-sdk/nextjs or @sitecore-content-sdk/angular) and prints each feature with its enabled status. Framework packages now export experimentalFeaturesCatalog from their /experimental entry. (e1d0156)

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

    • Add sitecore-tools project experimental list to show the experimental features available in the current Content SDK app.
      The command reads the app's framework package (@sitecore-content-sdk/nextjs or @sitecore-content-sdk/angular) and prints each feature with its enabled status. Framework packages now export experimentalFeaturesCatalog from their /experimental entry. (e1d0156)

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

    • [angular] Metadata, Open Graph and Schema.org & JSON-LD Support

    • @sitecore-content-sdk/content: resolvePageMetadataFields (with PageMetadataRouteFields / ResolvedPageMetadataFields) moved from @sitecore-content-sdk/nextjs to @sitecore-content-sdk/content/layout, so every framework shares the same field-to-tag rules. @sitecore-content-sdk/nextjs keeps re-exporting PageMetadataRouteFields.

    • @sitecore-content-sdk/angular: added PageMetadataService + <sc-page-meta-tags [route]> (<title>, metadata and Open Graph <meta> tags via Angular's Title/Meta services) and JsonLdSchemaService + <sc-json-ld-schema [page]> (a single <script type="application/ld+json"> in <head>, normal mode only). Re-exported the PageMetadataFields, MetadataFields, OpenGraphFields, OpenGraphImageField(Value) and PageMetadataRouteFields types.

    • Angular template: LayoutComponent renders both components; RouteFields extends PageMetadataFields. (c7801c3)

      • Schema.org & JSON-LD Support (b858df1)

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

    • Add sitecore-tools project experimental list to show the experimental features available in the current Content SDK app.
      The command reads the app's framework package (@sitecore-content-sdk/nextjs or @sitecore-content-sdk/angular) and prints each feature with its enabled status. Framework packages now export experimentalFeaturesCatalog from their /experimental entry. (e1d0156)
    • Schema.org & JSON-LD Support (b858df1)

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

    • Schema.org & JSON-LD Support (b858df1)

@github-actions

github-actions Bot commented Sep 10, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

📦 Package Size and Test Coverage Report

Package Base Size PR Size Δ Change Base Coverage PR Coverage Δ Change
analytics-core 69.05 KB 69.05 KB ✅ 0.00 KB 97.44% 97.44% 0.00%
angular 438.39 KB 438.39 KB ✅ 0.00 KB 94.22% 94.22% 0.00%
cli 84.63 KB 84.63 KB ✅ 0.00 KB 77.84% 77.84% 0.00%
content 525.88 KB 525.88 KB ✅ 0.00 KB 93.10% 93.10% 0.00%
core 139.38 KB 139.38 KB ✅ 0.00 KB 91.80% 91.80% 0.00%
create-content-sdk-app 551.42 KB 551.42 KB ✅ 0.00 KB 96.47% 96.47% 0.00%
events 72.33 KB 72.33 KB ✅ 0.00 KB 97.97% 97.97% 0.00%
nextjs 585.07 KB 585.07 KB ✅ 0.00 KB 91.79% 91.79% 0.00%
personalize 64.01 KB 64.01 KB ✅ 0.00 KB 99.74% 99.74% 0.00%
react 254.44 KB 254.44 KB ✅ 0.00 KB 93.83% 93.83% 0.00%
search 16.69 KB 16.69 KB ✅ 0.00 KB 98.89% 98.89% 0.00%
Total — — ✅ 0.00 KB — — —

@jss-release-github-app
jss-release-github-app Bot force-pushed the changeset-release/dev branch 4 times, most recently from 214bec6 to f17807e Compare September 14, 2026 10:17
@jss-release-github-app
jss-release-github-app Bot force-pushed the changeset-release/dev branch 3 times, most recently from 83e2aba to 5297362 Compare September 28, 2026 18:30
@jss-release-github-app
jss-release-github-app Bot force-pushed the changeset-release/dev branch 3 times, most recently from 225ac22 to 634f29b Compare October 6, 2026 18:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants