bc-telemetry-buddy-mcp 2.1.1 → 2.1.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 CHANGED
@@ -7,9 +7,21 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [2.1.2] - 2025-11-22
11
+
12
+ ### Fixed
13
+
14
+ - **Bundled Server Startup**: Fixed bundled server.js being executed twice causing startup failures
15
+ - Removed auto-execution code (`require.main === module` check) from server.ts
16
+ - Server now only starts when explicitly called via `startServer()` function
17
+ - Prevents CLI error messages when launched from VSCode extension
18
+ - Resolves issue where bundled server would exit with code 1 in VSCode
19
+
20
+ ## [2.1.1] - 2025-11-22
21
+
10
22
  ### Added
11
23
 
12
- - **Automatic Update Notifications**: MCP server now checks for updates on startup
24
+ - **Automatic Update Notifications**: MCP server checks for updates on startup
13
25
  - Queries npm registry for latest version asynchronously
14
26
  - Logs prominent warning banner when updates are available
15
27
  - Shows current version → latest version
@@ -17,16 +29,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
17
29
  - Non-blocking with 5-second timeout to avoid delaying startup
18
30
  - Silently fails on network errors (won't break offline usage)
19
31
 
20
- ## [2.1.1] - 2025-11-21
21
-
22
32
  ### Fixed
23
33
 
24
- - **MCP server startup failure**: Fixed issue where server would exit with code 1 when no config file exists
25
- - `loadConfigFromFile()` now returns `null` instead of throwing when no config is found
26
- - Server gracefully falls back to environment variables
34
+ - **Graceful Config Loading**: Server now handles missing config files gracefully
35
+ - `loadConfigFromFile()` returns `null` instead of throwing when no config is found
36
+ - Server falls back to environment variables when no config file exists
27
37
  - Removed problematic catch block that caused infinite loop on startup
28
- - Server now starts successfully and shows clear configuration warnings in logs
29
- - **CI build failure**: Fixed GitHub Actions build error where `version.js` wasn't generated before server build
38
+ - Server shows clear configuration warnings in logs but continues running
39
+ - **CI Build**: Fixed GitHub Actions build error
30
40
  - Added version generation script to `build:server` npm script
31
41
  - Both server and CLI builds now generate version file before bundling
32
42