viafrei 1.4.6 → 1.4.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/API.md +1 -1
- package/CHANGELOG.md +33 -0
- package/package.json +1 -1
package/API.md
CHANGED
|
@@ -17,7 +17,7 @@ server:** connect any MCP client and call `tools/list`.
|
|
|
17
17
|
|
|
18
18
|
| | |
|
|
19
19
|
| --- | --- |
|
|
20
|
-
| Server | `viafrei` 1.4.
|
|
20
|
+
| Server | `viafrei` 1.4.8 |
|
|
21
21
|
| MCP protocol | `2025-06-18` |
|
|
22
22
|
| Streamable HTTP | https://mcp.viafrei.de/mcp |
|
|
23
23
|
| Legacy HTTP+SSE | https://mcp.viafrei.de/sse |
|
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,39 @@ a Changelog and the versions follow Semantic Versioning.
|
|
|
7
7
|
|
|
8
8
|
Nothing yet.
|
|
9
9
|
|
|
10
|
+
## [1.4.8] - 2026-09-29
|
|
11
|
+
|
|
12
|
+
**A version-sync release.** The bridge is published at the version the ViaFrei server
|
|
13
|
+
is serving, so that `npx viafrei@X.Y.Z` and the endpoint it relays to are named by one
|
|
14
|
+
number. `mcp.viafrei.de` moved to `1.4.8`, so the bridge follows. 1.4.7 is absent from
|
|
15
|
+
the registry for the same reason 1.4.0–1.4.5 were: that platform version carried no
|
|
16
|
+
bridge change.
|
|
17
|
+
|
|
18
|
+
**Nothing in the bridge changed at all** — not the runtime, not the tooling, not a
|
|
19
|
+
gate. The diff against 1.4.6 is the three version fields plus the re-captured API
|
|
20
|
+
reference. If 1.4.6 works for you, this is the same code under a number that matches
|
|
21
|
+
the server.
|
|
22
|
+
|
|
23
|
+
### Changed
|
|
24
|
+
|
|
25
|
+
- **The API reference is re-captured at 1.4.8** (`API.md`, `catalogue.json`). Unlike
|
|
26
|
+
1.4.6's re-capture, this one is only a date and a version string: the server's
|
|
27
|
+
surface did **not** change between 1.4.6 and 1.4.8. Verified rather than assumed —
|
|
28
|
+
the same 19 tools, 10 resources, 2 resource templates and 9 prompts, with no tool
|
|
29
|
+
added or removed, no description altered and no `required` list moved, compared
|
|
30
|
+
field-by-field against the stored snapshot before the new one was written.
|
|
31
|
+
|
|
32
|
+
That distinction is the whole reason this entry says so out loud. At 1.4.6 the
|
|
33
|
+
shipped reference was *wrong* — it omitted a tool the server exposed. Here it was
|
|
34
|
+
merely *old*. The two need different remedies and only one of them is honest in each
|
|
35
|
+
case, so which one applied is recorded rather than left for a reader to guess.
|
|
36
|
+
|
|
37
|
+
Captured read-only: `initialize`, `tools/list`, `resources/list`,
|
|
38
|
+
`resources/templates/list`, `prompts/list`. No tool was invoked, so no data provider
|
|
39
|
+
was contacted, and the session was deleted afterwards. The two substitutions the
|
|
40
|
+
snapshot documents are unchanged and asserted on the way in and out: 19 of 19
|
|
41
|
+
`$schema` URIs dropped, exactly 2 long patterns stored as `patternLength`.
|
|
42
|
+
|
|
10
43
|
## [1.4.6] - 2026-09-29
|
|
11
44
|
|
|
12
45
|
**The version number is prod's, not this package's own count.** The bridge is released
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "viafrei",
|
|
3
|
-
"version": "1.4.
|
|
3
|
+
"version": "1.4.8",
|
|
4
4
|
"description": "German traffic, rail, parking, charging, fuel, address and weather data in your AI assistant - MCP, no API key. stdio bridge to the hosted ViaFrei MCP server.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"mcp",
|