@jmp-technologies/analytics 0.1.40 → 0.1.41

package/README.md

@@ -140,7 +140,7 @@ Place that in `app/robots.txt/route.ts` for Next.js App Router sites. Use `merge
 
 **Enforcement:** robots.txt is advisory. When this JMP setting is on, also add a `vercel.json` WAF deny (`jmpAiCrawlerVercelWafRoute()` or `create-jmp-client --block-ai-crawlers`) and set Vercel **AI Bots** to **deny**. Crawlers that spoof a normal browser or use undisclosed names may still access public pages. Generic Applebot is not WAF-denied so Apple Search can still crawl; `Applebot-Extended` is denied.
 
-Use **≥ 0.1.40** for the shared crawler list, robots merge helper, and WAF route helper.
+Use **≥ 0.1.41** for the shared crawler list, `mergeJmpRobotsTxt`, and WAF route helper (0.1.40 source had them; the published types did not).
 
 ---
 
@@ -359,6 +359,6 @@ After publish, on client sites:
 npm install @jmp-technologies/analytics@latest
 ```
 
-Use **≥ 0.1.8** for `getJmpSiteProfile` / `extras`. Use **≥ 0.1.10** for `email_click` tracking and `JmpTrackedMailtoLink`. Use **≥ 0.1.37** so server content fetches and server page views send `Origin` from `siteUrl` / `NEXT_PUBLIC_SITE_URL` (required for capabilities writes after the matching dashboard deploy). Use **≥ 0.1.38** so `contentManifest.routes` with wrapper `legal` or `pages` reports page URLs to the dashboard Pages tab. Use **≥ 0.1.39** so JMP content `fetch` uses the `jmp-content` cache tag (client webhooks revalidate it). Use **≥ 0.1.40** for AI crawler robots helpers and the Vercel WAF route helper.
+Use **≥ 0.1.8** for `getJmpSiteProfile` / `extras`. Use **≥ 0.1.10** for `email_click` tracking and `JmpTrackedMailtoLink`. Use **≥ 0.1.37** so server content fetches and server page views send `Origin` from `siteUrl` / `NEXT_PUBLIC_SITE_URL` (required for capabilities writes after the matching dashboard deploy). Use **≥ 0.1.38** so `contentManifest.routes` with wrapper `legal` or `pages` reports page URLs to the dashboard Pages tab. Use **≥ 0.1.39** so JMP content `fetch` uses the `jmp-content` cache tag (client webhooks revalidate it). Use **≥ 0.1.41** so npm types export `mergeJmpRobotsTxt`, `buildAiCrawlerRobotsTxt`, and the Vercel WAF route helper.
 
 Ensure the **dashboard** is deployed with migrations **020** and **021** and `/api/content/site` is live before relying on `getJmpSiteProfile` in production.

package/dist/astro/client.cjs

@@ -308,7 +308,7 @@ function extractMailtoTarget(href) {
 }
 
 // package.json
-var version = "0.1.40";
+var version = "0.1.41";
 
 // src/constants.ts
 var JMP_ANALYTICS_SDK_VERSION = version;