|
2 | 2 |
|
3 | 3 | All notable changes to this project will be documented in this file. |
4 | 4 |
|
5 | | -## Unreleased |
| 5 | +## [1.3.23] - 2026-08-16 |
6 | 6 |
|
7 | | -### Release metadata and security |
8 | | -- Kept `package.json`, `package-lock.json`, `server.json`, `glama.json` and the `src/index.ts` runtime declaration aligned at the published 1.3.22 release. A read-only npm check confirms version/latest `1.3.22`; no publish or registry write was performed. |
9 | | -- Raised the source and container contract to Node.js >=20 because the selected `@hono/node-server` 2.x dependency requires Node 20. The lockfile refresh closes the recorded `js-yaml`, `fast-uri`, `hono`, `ip-address` and nanoid advisories (`npm audit` clean). |
10 | | -- Documented that `glama.json` remains repository-only Glama directory metadata and is intentionally excluded from the npm `files` payload; `server.json` and `llms.txt` remain the shipped registry/discovery files. |
| 7 | +### Security |
11 | 8 | - Close the `js-yaml` advisory (quadratic CPU consumption in `!!omap` resolution, affecting 4.0.0-4.3.0) by raising the direct dependency to `^4.3.1`. |
| 9 | +- Close all open Dependabot advisories in lockfile (`ip-address`, `hono`, `fast-uri`, `nanoid`) — `npm audit` 100% clean. |
12 | 10 |
|
13 | | -### Fixed |
14 | | -- Realign `glama.json` with the published release: it had been left at 1.3.18 while `package.json`, `server.json`, `src/index.ts` and the npm release all moved to 1.3.22. The metadata test now covers `glama.json` too, so the directory manifest can no longer drift unnoticed. |
15 | | -- Raise the declared Node.js floor from 18 to 20 across `package.json` (`engines`), the lockfile, both READMEs and `llms.txt`. The CI matrix has only ever tested 20/22/24 and `@hono/node-server` 2.x requires 20, so the advertised `>=18` was wrong. |
| 11 | +### Maintenance & Packaging |
| 12 | +- Realigned `glama.json`, `package.json`, `server.json`, `src/index.ts` to `1.3.23`. |
| 13 | +- Included `glama.json` and `smithery.yaml` in package files and registry triad. |
| 14 | +- Raised declared Node.js floor from 18 to 20 across package metadata (`engines`), lockfile, READMEs and `llms.txt` (`@hono/node-server` 2.x requirement). |
16 | 15 |
|
17 | 16 | ### Discoverability & Metadata Parity |
18 | 17 | - Synchronized Shields.io test badges across `README.md` and `README_de.md` to reflect 176 Vitest tests and total 254 test assertions (176 Vitest unit tests, 35 MCP stdio integration tests, 43 i18n translation assertions). |
19 | 18 | - Expanded automated metadata test suite in `test/metadata.test.ts` (8/8 tests passed) validating manifest parity (`package.json`, `server.json`, `glama.json`, `src/index.ts`, `llms.txt`), presence of core documentation (`README.md`, `README_de.md`, `SECURITY.md`, `CHANGELOG.md`, `LICENSE`, `server.json`, `glama.json`, `llms.txt`), ecosystem & umbrella badges/links, and tool count assertions. |
20 | 19 | - Updated `llms.txt` Last-checked header to `2026-08-16` with full test suite metrics (254 tests passed) and updated ecosystem links including `open-bricks` and sibling MCP servers. |
21 | 20 |
|
22 | | -### Test gates |
| 21 | +### Test Gates |
23 | 22 | - Added `npm run test:integration` for the 35 real MCP stdio assertions and `npm run test:i18n` for the 43 translation assertions; GitHub Actions now runs both alongside the Vitest gate on Node.js 20, 22 and 24. |
24 | 23 | - Hardened the stdio harness so generated fixtures are removed on success, failures and termination, and the child process is terminated before the result is returned. |
25 | 24 |
|
|
0 commit comments