Surface API errors during CLI version checks - #26
Merged
Conversation
Route plain-text version responses through shared HTTP status handling so authorization and upstream errors are reported before semver parsing. Close response bodies, normalize valid version text, and cover success and failure cases.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Validation
go test ./...api.dev.wodby.comwith a placeholder invalid token now reportsUnknown authorization tokengit diff --checkOperational note
The failed staging workflow reached the dev API correctly but received HTTP 401. Its
WODBY_API_KEYstill needs to be replaced with a valid Wodby 1 dev API key.