You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Release QA on v0.47.0-rc.4 found the installed app reporting version
'development' on every httpapi-backed surface, with the Spec 079 update
banner, 'mcpproxy doctor' and 'mcpproxy status' all offering v0.46.0 —
a DOWNGRADE prompt — and telemetry heartbeats reporting 'development'
(corrupting Spec 080 churn metrics for the whole RC channel).
Two root causes, both fixed:
1. Wrong/missing -X ldflags paths. Go silently ignores -X with a wrong
package path; the module is github.com/smart-mcp-proxy/mcpproxy-go:
- prerelease.yml used mcpproxy-go/internal/httpapi.buildVersion
(ignored) and the bogus mcpproxy-go/cmd/mcpproxy.version → every
RC binary shipped with buildVersion='development'
- scripts/build-windows-installer.ps1 (used by BOTH release.yml and
prerelease.yml) never set httpapi.buildVersion → stable Windows
installer builds have the same bug
- scripts/build.ps1 and pr-build.yml aligned for consistency
2. Checker.CheckNow() (the /api/v1/info forced-refresh path used by the
Web UI banner and doctor) lacked the non-semver guard that Start()
has, and compareVersions() ranks an invalid current version below
any release. A 'development' build therefore saw every stable
release as an available 'update'. CheckNow now skips like Start,
and compareVersions returns false for a non-semver current version.
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
0 commit comments