@yawlabs/lemonsqueezy-mcp 0.14.0 → 0.14.2

package/CHANGELOG.md

@@ -1,5 +1,29 @@
 # Changelog
 
+## [Unreleased]
+
+## [0.14.2] — 2026-09-14
+
+### Security
+
+- **The `@modelcontextprotocol/sdk` devDependency moves from `^1.29.0` to `^1.30.0`, and `npm audit` is clean again (it reported 6 findings, 2 high).** The SDK's transitive dependencies all move past their advisories: `fast-uri` 3.1.2 -> 3.1.7, `hono` 4.12.26 -> 4.13.7 (the existing `hono` override floor goes from `^4.12.14` to `^4.13.5`, the first patched version), `@hono/node-server` 1.19.13 -> 2.1.1, `ip-address` 10.2.0 -> 10.7.0, `qs` 6.15.2 -> 6.16.0 and `body-parser` 2.2.2 -> 2.3.0. Only `fast-uri` (via `ajv`) is bundled into the published `dist/index.js`, and the 0.14.1 bundle carried 3.1.2, inside the advised range; the others never reach the bundle, because the server uses only the SDK's stdio transport.
+
+## [0.14.1] — 2026-09-14
+
+### Changed
+
+- npm and MCP Registry listing metadata: bugs URL, core keywords, and server.json title/repository/websiteUrl
+- **`release.sh` writes a `## [x.y.z]` changelog entry for every release and takes the GitHub release notes from it.** `[Unreleased]` is promoted when it has content, with a fresh empty `[Unreleased]` heading left above the new section for the next change; when it is empty or absent, the section is generated from the commit subjects since the previous tag instead of being skipped. The Keep-a-Changelog link references at the bottom are moved along with it (`[Unreleased]` compares from the new tag and the version gets its own compare link), and the release fails when the entry is missing for any reason. Before this, a release with nothing under `[Unreleased]` got no entry at all -- 0.14.0 below is backfilled -- and its GitHub release page showed raw commit subjects.
+
+## [0.14.0] — 2026-09-13
+
+No runtime changes: nothing under `src/` changed and no dependency moved. This release is release tooling and docs. This entry was backfilled -- `[Unreleased]` was empty when 0.14.0 was cut, so its GitHub release notes fell back to bare commit subjects.
+
+### Changed
+
+- **`release.sh` waits for npm to serve the new version before publishing to the MCP Registry.** `npm publish` returns as soon as the registry accepts the tarball, but the version is not yet readable from npm's CDN-backed read path, and the MCP Registry validates a publish by reading it -- so a registry publish run straight after `npm publish` could fail with `version 'X' was not found (status: 404)` and the release needed a second invocation (ssh-mcp v0.15.3 failed that way, and aws-mcp did on three consecutive releases). Step 7 now polls the exact URL the registry's npm validator builds, `https://registry.npmjs.org/@yawlabs%2Flemonsqueezy-mcp/<version>` with the scope slash escaped the way Go's `url.PathEscape` does, using `curl` rather than `npm view`, whose 5-minute metadata cache can outlast the condition. A timeout warns rather than fails, so `mcp-publisher` still reports its own precise error; `SKIP_NPM_WAIT=1` bypasses the wait, `NPM_WAIT_TIMEOUT_S` retunes the 300s default, and a missing `curl` skips it with a warning (#50).
+- **README:** the X follow badge moved from the top of the page to the bottom, so the description leads on npm and GitHub (#51).
+
 ## [0.13.5] — 2026-09-13
 
 ### Fixed
@@ -610,7 +634,12 @@ Hardening pass for unattended automation against live billing flows.
 
 Initial release. 59 tools covering all 17 LemonSqueezy API resources.
 
-[Unreleased]: https://github.com/YawLabs/lemonsqueezy-mcp/compare/v0.13.3...HEAD
+[Unreleased]: https://github.com/YawLabs/lemonsqueezy-mcp/compare/v0.14.2...HEAD
+[0.14.2]: https://github.com/YawLabs/lemonsqueezy-mcp/compare/v0.14.1...v0.14.2
+[0.14.1]: https://github.com/YawLabs/lemonsqueezy-mcp/compare/v0.14.0...v0.14.1
+[0.14.0]: https://github.com/YawLabs/lemonsqueezy-mcp/compare/v0.13.5...v0.14.0
+[0.13.5]: https://github.com/YawLabs/lemonsqueezy-mcp/compare/v0.13.4...v0.13.5
+[0.13.4]: https://github.com/YawLabs/lemonsqueezy-mcp/compare/v0.13.3...v0.13.4
 [0.13.3]: https://github.com/YawLabs/lemonsqueezy-mcp/compare/v0.13.2...v0.13.3
 [0.13.2]: https://github.com/YawLabs/lemonsqueezy-mcp/compare/v0.13.1...v0.13.2
 [0.13.1]: https://github.com/YawLabs/lemonsqueezy-mcp/compare/v0.13.0...v0.13.1

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 Yaw Labs
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 Yaw Labs
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.