@contentrain/emitter-astro 0.18.61 → 0.18.62

package/README.md

@@ -319,3 +319,7 @@ literal routes.
 ## Checking the emitted types
 
 The unit suite asserts what the emitter writes; `pnpm --filter @contentrain/emitter-astro test:astro` (after `pnpm build`) checks it the way a migrated site's build does. It emits a site with every kind of page and endpoint — posts, pages, nested category and tag archives with their feeds, an author profile, a list, a static page, the feed, llms.txt, redirects, and a draft, an entry in review, a post scheduled for later and password-protected and private posts beside published ones — once with trailing slashes and once without, installs it with npm from its own `package.json` the way a production host does (`NODE_ENV=production`, `CI` set, no terminal), and runs `astro check` and then the site's own `npm run build`. A pass is a result naming 0 errors and a completed build; Astro's "requires @astrojs/check" notice fails it even though Astro exits 0 there. The first site is then built with `astro build`, and the output is read: the published posts have pages, sitemap lines and feed items, the held-back ones have none (nor llms.txt links or list cards), no file holds the password-protected post's text, and the live page's links to held-back entries are text. CI and the release workflow run it on every change.
+
+## License
+
+MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@contentrain/emitter-astro",
-  "version": "0.18.61",
+  "version": "0.18.62",
   "license": "MIT",
   "description": "Open Astro emitter for Contentrain migrations — renders a ProjectIR into a working Astro project",
   "type": "module",
@@ -37,7 +37,7 @@
     "dist"
   ],
   "dependencies": {
-    "@contentrain/types": "1.78.0"
+    "@contentrain/types": "1.78.1"
   },
   "devDependencies": {
     "@types/node": "^22.10.0",