bc-telemetry-buddy-mcp 2.0.5 → 2.1.1

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,6 +7,46 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ### Added
11
+
12
+ - **Automatic Update Notifications**: MCP server now checks for updates on startup
13
+ - Queries npm registry for latest version asynchronously
14
+ - Logs prominent warning banner when updates are available
15
+ - Shows current version → latest version
16
+ - Provides update instructions (npm install and VSCode command)
17
+ - Non-blocking with 5-second timeout to avoid delaying startup
18
+ - Silently fails on network errors (won't break offline usage)
19
+
20
+ ## [2.1.1] - 2025-11-21
21
+
22
+ ### Fixed
23
+
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
27
+ - 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
30
+ - Added version generation script to `build:server` npm script
31
+ - Both server and CLI builds now generate version file before bundling
32
+
33
+ ## [2.1.0] - 2025-11-21
34
+
35
+ ### Added
36
+
37
+ - New features and improvements (minor release)
38
+
39
+ ### Changed
40
+
41
+ - **Graceful startup with incomplete configuration**: MCP server now starts successfully even when configuration is incomplete, instead of failing with exit code 1
42
+ - Configuration validation moved from startup (throwing errors) to runtime (returning helpful error messages through MCP interface)
43
+ - Error messages are now MCP-client agnostic, providing guidance for both VSCode extension users and standalone MCP client users (Claude Desktop, etc.)
44
+
45
+ ### Fixed
46
+
47
+ - Server no longer fails to start in workspaces without BC Telemetry Buddy configuration
48
+ - Missing `BCTB_WORKSPACE_PATH` now uses `process.cwd()` as fallback instead of throwing error
49
+
10
50
  ## [2.0.5] - 2025-11-19
11
51
 
12
52
  ### Fixed