[csdk] latest release

[jss-release-github-app]

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

• minor @sitecore-content-sdk/content dependency update:
  • Schema.org & JSON-LD Support (b858df1)

Patch Changes

• 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: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

• minor @sitecore-content-sdk/content dependency update:
  • Schema.org & JSON-LD Support (b858df1)

@sitecore-content-sdk/content@2.4.0

Minor Changes

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

Patch Changes

• 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

• Schema.org & JSON-LD Support (b858df1)
• minor @sitecore-content-sdk/content dependency update:
  • Schema.org & JSON-LD Support (b858df1)
• minor @sitecore-content-sdk/react dependency update:
  • Schema.org & JSON-LD Support (b858df1)

Patch Changes

• 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: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:
  • Schema.org & JSON-LD Support (b858df1)

create-content-sdk-app@2.4.1

Patch Changes

• 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.

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

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

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

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

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

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

[github-actions]

📦 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	421.74 KB	421.74 KB	✅ 0.00 KB	94.08%	94.08%	0.00%
cli	63.35 KB	63.35 KB	✅ 0.00 KB	73.80%	73.80%	0.00%
content	517.53 KB	517.53 KB	✅ 0.00 KB	93.16%	93.16%	0.00%
core	139.38 KB	139.38 KB	✅ 0.00 KB	91.80%	91.80%	0.00%
create-content-sdk-app	549.69 KB	549.69 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	589.52 KB	589.52 KB	✅ 0.00 KB	91.97%	91.97%	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	—	—	—