fix: Add refresh option to update check for doctor command #213
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
mcpproxy doctorshowing stale update information when a new release was published after the last periodic check?refresh=truequery parameter to/api/v1/infoendpoint to force immediate update checkProblem
When running
mcpproxy doctor, users were seeing cached update information from the 4-hour periodic check. If a new version was released after the last check, users would not be notified until the next periodic check ran.Example: v0.11.3 was released, but doctor showed v0.11.2 as latest because the last check happened before the release.
Solution
CheckNow()method to update checker for on-demand checksRefreshVersionInfo()method through the stack (Runtime, Server, Controller)/api/v1/infoendpoint to acceptrefresh=truequery parameterTest plan
CheckNow()method in update checker🤖 Generated with Claude Code