qyl-mcp-server 4.0.0 → 5.0.0
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/README.md +31 -1
- package/dist/mcp-app.html +1 -1
- package/dist/mcp-dashboard.html +1 -1
- package/dist/mcp-home.html +1 -1
- package/package.json +15 -15
package/README.md
CHANGED
|
@@ -75,12 +75,42 @@ multi-tenant audit log.
|
|
|
75
75
|
Secrets are redacted before results reach the model, structured content, or
|
|
76
76
|
durable evidence.
|
|
77
77
|
|
|
78
|
-
`--stdio` runs under Node.js 24 or Bun 1.
|
|
78
|
+
`--stdio` runs under Node.js 24 or Bun 1.4, which is what `npx` gives you.
|
|
79
79
|
The HTTP entry is a web-standard fetch handler served by its default export,
|
|
80
80
|
so serving it requires Bun.
|
|
81
81
|
|
|
82
82
|
## Release notes
|
|
83
83
|
|
|
84
|
+
### 5.0.0
|
|
85
|
+
|
|
86
|
+
- **Breaking.** Contract major: `@ancplua/qyl-api-schema` 9.0.0 -> 10.0.0,
|
|
87
|
+
revision `sha256:d1c859393b628164` -> `sha256:264a9e4f1d70289a`. The
|
|
88
|
+
startup handshake refuses a collector that advertises anything else, so
|
|
89
|
+
this server and the collector move together.
|
|
90
|
+
- The contract's revision scheme moved to `qyl-contract-revision-v3`; the
|
|
91
|
+
revision string is read from the package at build time, so nothing in this
|
|
92
|
+
server encodes it by hand.
|
|
93
|
+
- The contract's `./generated/otel-keys` TypeSpec keys projection was
|
|
94
|
+
removed upstream. This server never imported it — the tool surface,
|
|
95
|
+
schemas, and protocol are unchanged, and
|
|
96
|
+
`server/tool-manifest.snapshot.json` differs only in its
|
|
97
|
+
`contract_revision`.
|
|
98
|
+
|
|
99
|
+
### 4.0.1
|
|
100
|
+
|
|
101
|
+
- Dependencies only; no tool, schema, or protocol change. The published
|
|
102
|
+
package's runtime dependencies move to their latest stable versions, so
|
|
103
|
+
the tarball no longer describes a tree that has since moved on.
|
|
104
|
+
- OpenTelemetry: `@opentelemetry/api-logs`, `exporter-logs-otlp-proto`,
|
|
105
|
+
`exporter-metrics-otlp-proto`, `exporter-trace-otlp-proto` and `sdk-logs`
|
|
106
|
+
`^0.221.0` -> `^0.222.0`; `core`, `resources`, `sdk-metrics`,
|
|
107
|
+
`sdk-trace-base` and `sdk-trace-node` `^2.10.0` -> `^2.11.0`.
|
|
108
|
+
- `jose` `^6.2.3` -> `^6.2.10`, `zod` `^4.5.0` -> `^4.5.4`.
|
|
109
|
+
- `@ancplua/qyl-api-schema` stays 9.0.0, revision
|
|
110
|
+
`sha256:d1c859393b628164`, and `@opentelemetry/semantic-conventions`
|
|
111
|
+
stays `^1.43.0` — the contract and the startup handshake are unchanged,
|
|
112
|
+
so this server and the collector do not have to move together.
|
|
113
|
+
|
|
84
114
|
### 4.0.0
|
|
85
115
|
|
|
86
116
|
- **Breaking.** The Codex workflow tools are gone: `list_workflow_runs`,
|