create-content-sdk-app 2.4.1-canary.20260910100657 → 2.4.1

package/dist/templates/nextjs-app-router-cache-components/.agents/docs/AGENTS-key-concepts.md

@@ -11,8 +11,7 @@ Optional, on-demand detail. The compact guide is [AGENTS.md](../../AGENTS.md).
   - `getSitecoreErrorPage({ site, locale, code })` → 404 / 500 Sitecore content with the same tag strategy as `getSitecorePage`.
 - **`POST /api/revalidate`** is a single Sitecore-webhook endpoint. It accepts the Sitecore Experience Edge / Content Operations payload shape:
   - `updates[]` — Sitecore publish-event rows; the handler maps each row's `identifier` (with `-media` / `-layout` stripped) to `sc:item:<id>:<locale>`.
-  - `tags[]` — pass-through array. `sc:`-prefixed strings are revalidated verbatim (handy for ad-hoc, operational calls); bare item IDs are mapped to `sc:item:<id>:<defaultLocale>`.
-  - Dictionary tags from `sites` (`.sitecore/sites.json`; configured `defaultSite` from `generateSites` only when `NEXT_PUBLIC_DEFAULT_SITE_NAME` is set) are merged on every call so dictionary changes are covered.
+  - Dictionary entry updates (`entity_definition: "DictionaryEntry"`) map to `sc:dict:<site>:<locale>` for the specific site resolved from the identifier via `sites` (`.sitecore/sites.json`; configured `defaultSite` from `generateSites` only when `NEXT_PUBLIC_DEFAULT_SITE_NAME` is set) — only that site's dictionary tag is revalidated, not every configured site's.
 - **Auth (optional):** leave `SITECORE_REVALIDATE_SECRET` empty to skip auth (no `x-revalidate-secret` header). When set, callers must send the same value in `x-revalidate-secret` (configure that header on your Sitecore webhook).
 - **Dictionary cache:** `sitecore.config.ts` disables the SDK's in-process dictionary cache (`dictionary: { caching: { enabled: false } }`). The Cache Components helper is the only dictionary cache layer, so `revalidateTag` works end to end.
 

package/dist/templates/nextjs-app-router-cache-components/.agents/docs/AGENTS-router-specifics.md

@@ -40,8 +40,7 @@ Optional, on-demand detail. The compact guide is [AGENTS.md](../../AGENTS.md).
 
 - **Where:** `src/app/api/revalidate/route.ts`. Uses `createSitecoreRevalidateRouteHandler` from `@sitecore-content-sdk/nextjs/route-handler` — a single Sitecore-webhook endpoint.
 - **Auth:** When `SITECORE_REVALIDATE_SECRET` is non-empty, callers must send the same value in `x-revalidate-secret`. When empty, revalidation works without that header.
-- **Webhook payload (`updates[]`):** Send the Sitecore Experience Edge / Content Operations body (`updates`, `invocation_id`, `continues`). The handler maps each `identifier` (with `-media` / `-layout` stripped) to `sc:item:<id>:<locale>` and revalidates it.
-- **Ad-hoc invalidation (`tags[]`):** Reuse the same endpoint with `{ "tags": ["sc:route:...", "sc:item:..."] }` (`sc:`-prefixed strings are revalidated verbatim) or `{ "tags": ["<itemId>"] }` (bare item IDs are mapped to `sc:item:<id>:<defaultLocale>`). Dictionary tags from `sites` are appended on **every** call.
+- **Webhook payload (`updates[]`):** Send the Sitecore Experience Edge / Content Operations body (`updates`, `invocation_id`, `continues`). The handler maps each `identifier` (with `-media` / `-layout` stripped) to `sc:item:<id>:<locale>` and revalidates it. A Dictionary entry update (`entity_definition: "DictionaryEntry"`) instead revalidates `sc:dict:<site>:<locale>` for the specific site resolved from the identifier via `sites` — not every configured site's.
 - **Do not:** Bypass auth, expose the secret in client code, or call `revalidateTag` directly from components.
 
 ## Server vs Client components

package/dist/templates/nextjs-app-router-cache-components/.agents/skills/content-sdk-cache-components-and-osr/SKILL.md

@@ -17,7 +17,7 @@ description: Tag-based caching in src/lib/cache/ and POST /api/revalidate webhoo
 ## Rules
 
 - Cache helpers use `'use cache'` + `cacheTag` with `sc:route` / `sc:item` / `sc:dict` tags
-- `POST /api/revalidate` accepts `updates[]` and `tags[]`
+- `POST /api/revalidate` accepts `updates[]`
 - Optional `SITECORE_REVALIDATE_SECRET` + `x-revalidate-secret` header
 - Do not call `revalidateTag` from components
 

package/dist/templates/nextjs-app-router-cache-components/src/app/api/revalidate/route.ts

@@ -1,7 +1,6 @@
 /**
  * POST /api/revalidate — Sitecore webhook (Experience Edge / Content Operations) endpoint.
- * Also accepts ad-hoc `tags[]` (`sc:`-prefixed strings or bare item IDs). See SDK
- * `createSitecoreRevalidateRouteHandler` for the full payload contract.
+ * See SDK `createSitecoreRevalidateRouteHandler` for the full payload contract.
  *
  * Dictionary tags are derived from `.sitecore/sites.json` (includes the default site from `generateSites`).
  */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-content-sdk-app",
-  "version": "2.4.1-canary.20260910100657",
+  "version": "2.4.1",
   "description": "Sitecore Content SDK initializer",
   "bin": "./dist/index.js",
   "scripts": {
@@ -39,10 +39,10 @@
   },
   "devDependencies": {
     "@sitecore-content-sdk/analytics-core": "^2.1.2",
-    "@sitecore-content-sdk/angular": "1.0.1-canary.20260910100657",
-    "@sitecore-content-sdk/cli": "2.3.1-canary.20260910100657",
+    "@sitecore-content-sdk/angular": "~1.0.1",
+    "@sitecore-content-sdk/cli": "^2.3.0",
     "@sitecore-content-sdk/events": "^2.1.2",
-    "@sitecore-content-sdk/nextjs": "2.4.1-canary.20260910100657",
+    "@sitecore-content-sdk/nextjs": "^2.4.1",
     "@sitecore-content-sdk/personalize": "^2.1.0",
     "@stylistic/eslint-plugin": "^5.2.2",
     "@types/chai": "^5.2.2",