bc-telemetry-buddy-mcp 3.7.1 → 3.7.2
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/CHANGELOG.md +10 -0
- package/dist/cli.js +1973 -307
- package/dist/server.js +1919 -253
- package/package.json +3 -3
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [3.7.2] - 2026-10-23
|
|
11
|
+
|
|
12
|
+
_Highest blast-radius rating across all plans landed in this release: `low-risk`._
|
|
13
|
+
|
|
14
|
+
### Security
|
|
15
|
+
- Runtime dependency security fixes ([#135](https://github.com/waldo1001/waldo.BCTelemetryBuddy/issues/135)), all within the current major versions: `proxy-addr` 2.0.8 (critical, via `express` ^4.22.3), `axios` ^1.20.0, `follow-redirects` 1.16.1, `@modelcontextprotocol/sdk` ^1.32.1, `fast-uri` 3.1.9, `ip-address` 10.7.4, `@grpc/grpc-js` 1.14.6, and the OpenTelemetry / Azure Monitor stack (`applicationinsights` 3.17.0). `npm audit --omit=dev` now reports no high or critical findings.
|
|
16
|
+
|
|
17
|
+
### Changed
|
|
18
|
+
- Published through **npm Trusted Publishing (OIDC)** with provenance; the long-lived `NPM_TOKEN` is gone ([#137](https://github.com/waldo1001/waldo.BCTelemetryBuddy/issues/137)). The release workflows run all `actions/*` on their Node 24 majors, and the npm check after publishing retries for up to 5 minutes instead of reporting a false 404.
|
|
19
|
+
|
|
10
20
|
## [3.7.1] - 2026-10-23
|
|
11
21
|
|
|
12
22
|
_Highest blast-radius rating across all plans landed in this release: `low-risk`._
|