leglas-mcp 0.8.0 → 0.9.0

package/README.md

@@ -12,6 +12,7 @@
   <a href="https://www.npmjs.com/package/leglas"><img src="https://img.shields.io/npm/v/leglas" alt="npm"></a>
   <a href="https://github.com/FredAmartey/leglas/actions/workflows/ci.yml"><img src="https://github.com/FredAmartey/leglas/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
   <a href="LICENSE"><img src="https://img.shields.io/npm/l/leglas" alt="license"></a>
+  <a href="https://leglas.vercel.app/changelog/"><img src="https://img.shields.io/badge/changelog-what's%20new-0B1839" alt="changelog"></a>
 </p>
 
 <p align="center">
@@ -534,6 +535,7 @@ pnpm install
 pnpm build       # build every package
 pnpm test        # run the test suite
 pnpm typecheck   # type check every package
+pnpm site        # build the site, homepage and changelog, into dist/site
 ```
 
 | Package           | Contents                                           |
@@ -549,11 +551,18 @@ terminal and `pnpm --filter @leglas/shell dev` in another.
 Two packages are published, both unscoped: `leglas`, which bundles the
 server and the built interface, and `leglas-mcp`. Releases are
 tag-driven: set the same version in both packages and `plugin.json`, turn
-the changelog's Unreleased section into that version, push a `v<version>`
-tag, and CI runs the suite and publishes through npm trusted publishing.
-A tag that disagrees with the manifests is refused, and so is a patch tag
-when `api-surface.txt` has moved since the previous one. No npm token
-exists anywhere in the project.
+the changelog's Unreleased section into that version with a title for what
+the release was about, push a `v<version>` tag, and CI runs the suite and
+publishes through npm trusted publishing. A tag that disagrees with the
+manifests is refused, and so is a patch tag when `api-surface.txt` has
+moved since the previous one. No npm token exists anywhere in the project.
+
+The [site](https://leglas.vercel.app/) is two pages, the homepage and the
+[changelog](https://leglas.vercel.app/changelog/), written by `site.ts`. The
+changelog page is made from `CHANGELOG.md` and nothing else, so describing a
+release in the changelog is the whole job. Vercel builds it from
+`vercel.json` on every push, so main is the live site and every pull request
+gets a preview.
 
 ## License
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "leglas-mcp",
-  "version": "0.8.0",
+  "version": "0.9.0",
   "description": "Stdio MCP server exposing Leglas to agent hosts that cannot run a shell.",
   "type": "module",
   "bin": {
@@ -15,7 +15,7 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.30.0",
     "zod": "^3.25.76",
-    "leglas": "^0.8.0"
+    "leglas": "^0.9.0"
   },
   "license": "MIT",
   "repository": {