@se-studio/skills 1.1.1 → 1.1.3

package/CHANGELOG.md

@@ -1,5 +1,29 @@
 # @se-studio/skills
 
+## 1.1.3
+
+### Patch Changes
+
+- Bulk version bump: patch for all packages
+
+## 1.1.2
+
+### Patch Changes
+
+- Exclude redirect sources from sitemaps + robust protection against self and circular redirects.
+
+  - `buildRedirectMap` now normalizes internal paths (leading + trailing `/` to match urlCalculators + sitemap conventions) and reliably drops self-redirects (A → A). It also detects longer redirect cycles (A → B → A, etc.), drops the participating `from` rules from the baked map, and emits a `console.warn` during construction (visible in build/generate scripts).
+  - New exported utility: `filterSitemapEntriesExcludingRedirects(entries, redirectMap)`. Works on any `{ url: string }[]` (SitemapEntry, ISitemapEntry, etc.).
+  - The standard marketing site sitemap helper now accepts an optional `redirectMap` in `getSitemapEntries({ includeUnindexed, redirectMap })`. When provided, any URL that is the source of an active redirect is excluded from the generated sitemap entries. This is the recommended way to keep sitemaps clean when using editor-managed redirects.
+  - Widened the public `getSitemapEntries` option type in app helpers (additive; existing callers unaffected).
+  - Updated example app sitemaps (main + unindexed) to demonstrate fetching the map and passing it.
+  - Skill docs (`se-marketing-sites-redirects`) now include a "Redirects and sitemaps" section with usage patterns + notes on the improved cycle/self protection. Also updated routing docs.
+  - `buildRedirectMap` / `RedirectMap` / `getRedirectMap` behaviour for the middleware baked map is now safer (no self-loops or cycles will be baked).
+
+  Consumers using the `marketingSiteSitemap` helper + `getRedirectMap` at build time can now easily exclude redirect sources from both their static redirect map (for middleware) and their sitemaps in one consistent way.
+
+  See the redirect skill for the full recommended build-time pattern and the new filter helper.
+
 ## 1.1.1
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@se-studio/skills",
-  "version": "1.1.1",
+  "version": "1.1.3",
   "description": "SE Studio agent skills for marketing site development with Contentful CMS",
   "repository": {
     "type": "git",

package/skills/se-marketing-sites-redirects/SKILL.md

@@ -60,7 +60,7 @@ The following are already in the packages:
 
 - `IRedirect` + `isRedirect` in `@se-studio/core-data-types` (now uses `fromInternal` / `toInternal`)
 - `baseRedirectConverter` + `BaseRedirectSkeleton`
-- `contentfulRedirectsRest` + `buildRedirectMap` + `getRedirectsWithErrors` / `getRedirectMap` (via `createAppHelpers`)
+- `contentfulRedirectsRest` + `buildRedirectMap` (now with robust self/cycle guards + normalization) + `getRedirectsWithErrors` / `getRedirectMap` (via `createAppHelpers`)
 - Revalidation tag `redirect` (so the existing webhook machinery knows about the new type)
 
 You only need to wire the **rebuild** side in your app.
@@ -174,6 +174,30 @@ export const config = {
 
 If you already have a `middleware.ts` for A/B or other things, just add the redirect check at the very top (before any other logic).
 
+### 4.2.1 Redirects and sitemaps
+
+When you create a redirect whose `from` (raw or resolved via internal picker) matches a URL that would otherwise be listed in your sitemap, that URL should generally be omitted from the sitemap (search engines should not be told to crawl a source that 301s away).
+
+The shared libraries now support this easily:
+
+- The `getSitemapEntries(...)` function returned by the marketing sitemap helper (when you configure `marketingSiteSitemap` in `createAppHelpers`) accepts an optional `redirectMap` in its options. When supplied, any entry whose URL is a redirect source is filtered out before the entries are returned to `buildSitemap`.
+- Standalone: `filterSitemapEntriesExcludingRedirects(entries, redirectMap)` (exported from `@se-studio/contentful-rest-api`) works on any `{ url: string }[]` list for custom flows.
+
+Recommended pattern (in `app/sitemap.ts` and the unindexed route):
+
+```ts
+import { getRedirectMap, getSitemapEntries } from '@/lib/cms-server';
+import { buildSitemap } from '@se-studio/core-ui';
+
+export default async function sitemap() {
+  const redirectMap = await getRedirectMap({});
+  const entries = await getSitemapEntries({ includeUnindexed: false, redirectMap });
+  return buildSitemap([() => Promise.resolve(entries)], { baseUrl, ... });
+}
+```
+
+Pure `fromPath` vanity redirects were already absent from sitemaps (no backing content entry). This mainly helps when you redirect *away from* live CMS pages/articles.
+
 ### 4.3 Webhook = Deploy Hook (the trigger)
 
 In Contentful → Settings → Webhooks, create (or reuse) a webhook that fires on:
@@ -226,6 +250,8 @@ Then commit the updated `.agents/skills/...` (the monorepo keeps them in sync wi
 
 The `redirect` content type and the `buildRedirectMap` / `getRedirectMap` helpers are intentionally stable so a future faster path can consume the same data.
 
+`buildRedirectMap` automatically drops self-redirects (A → A after normalization) and any rules that participate in longer cycles, emitting a console warning for cycles during build/generate. Internal paths are normalized with a trailing `/` to match your urlCalculators and sitemap hrefs.
+
 ---
 
 **You now have editor-managed redirects that are as robust and low-surprise as your A/B tests, using only patterns that already exist in the codebase.**