viafrei 0.0.9 → 1.3.12

package/CHANGELOG.md

@@ -3,6 +3,45 @@
 All notable changes to this package are documented here. The format follows Keep
 a Changelog and the versions follow Semantic Versioning.
 
+## [1.3.12] - 2026-09-23
+
+The bridge's code is unchanged since 0.0.9. This release replaces 1.3.10,
+which was published and then withdrawn from npm.
+
+**Why 1.3.12.** npm never lets a version number be used twice, even after an
+unpublish, so 1.3.10 cannot come back. This release is numbered 1.3.12, and
+1.3.11 is not used by this package. Everything 1.3.10 described below still
+applies to this release: the same code, the same README.
+
+**If you pinned 1.3.10,** move the pin to 1.3.12. Anyone who used `npx -y viafrei`
+without a version got 0.0.9 while 1.3.10 was withdrawn, and gets 1.3.12 from now
+on. Nothing about the connection changes: all three versions relay to the same
+endpoint in the same way.
+
+### Changed
+
+- **The version is 1.3.12.** No other change to the published files.
+
+## [1.3.10] - 2026-09-23 [YANKED]
+
+The bridge's code is unchanged since 0.0.9; this release exists so that its
+number matches the endpoint it connects to again.
+
+**Why 1.3.10, straight from 0.0.9.** The bridge tracks the platform, and the
+hosted endpoint now reports `serverInfo.version` 1.3.10. The platform moved
+through 0.1.x and 1.x without the bridge needing to change, so no bridge was
+published for those numbers, and none will be: a version is only cut when
+there is something to install. The versions in between are not skipped
+releases of this package; they never existed here.
+
+### Changed
+
+- **The README says which clients need this package, and which do not.** The
+  server now also answers the older HTTP+SSE transport at
+  `https://mcp.viafrei.de/sse`, so a client that speaks only HTTP+SSE can connect
+  directly. The bridge is for stdio-only clients and nobody else, and the page
+  now says so instead of "most clients".
+
 ## [0.0.9] - 2026-09-21
 
 The first release with code in it.
@@ -227,4 +266,6 @@ for it, so the number is free; the bridge will use it when the platform does.
   commits, and a squash makes them unreachable from `main` - which would turn
   the check red on `main` for everybody, for something no contributor did.
 
+[1.3.12]: https://github.com/mavrovde/viafrei-bridge/releases/tag/v1.3.12
+[1.3.10]: https://github.com/mavrovde/viafrei-bridge/releases/tag/v1.3.10
 [0.0.9]: https://github.com/mavrovde/viafrei-bridge/releases/tag/v0.0.9

package/README.md

@@ -91,10 +91,15 @@ Probably not — and that is deliberate.
 Most MCP clients speak Streamable HTTP and should connect straight to
 `https://mcp.viafrei.de/mcp`. **They do not need this package at all.**
 
-Some clients still speak only stdio. This bridge is for those: it runs locally,
-exposes a stdio MCP server, and relays every request to the public endpoint. It
-is a transport shim — it holds no data and no credentials, and it makes no
-decision about any answer.
+Clients that speak only the older HTTP+SSE transport do not need it either: the
+server answers that transport too, at `https://mcp.viafrei.de/sse`
+(`claude mcp add --transport sse`). It is deprecated in the specification and
+carried so that nobody meets a locked door; prefer the address above.
+
+Some clients still speak only stdio. **This bridge is for those** — and only
+those: it runs locally, exposes a stdio MCP server, and relays every request to
+the public endpoint. It is a transport shim: it holds no data and no
+credentials, and it makes no decision about any answer.
 
 ## Configuration
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "viafrei",
-  "version": "0.0.9",
+  "version": "1.3.12",
   "description": "stdio<->Streamable-HTTP bridge for the ViaFrei MCP server - German road, rail, parking, charging and fuel data for stdio-only MCP clients",
   "keywords": [
     "mcp",