chore(deps): bump zad-cli to v0.8.0#50
Merged
Merged
Conversation
v0.8.0 verving het platte {error,status_code} JSON-formaat door een
diagnose-object (headline, summary, next_steps, fault). report_zad_error
leest nu die velden en valt terug op .error voor version-skew, zodat
netwerk- en onbekende fouten hun boodschap behouden in plaats van leeg
te tonen.
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
1 participant
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.
Bumps the pinned zad-cli from v0.6.0 to v0.8.0.
What's in v0.8.0
admin orphan-report/admin orphan-confirmcommands (the orphan sweep)fault, source label, headline, summary and next steps, with CI exit codes (1 = your fault, 2 = transient, 3 = unknown)Why the parser changes
v0.8.0 replaced the flat
{"error": "...", "status_code": N}JSON error with the diagnosis object (headline,summary,next_steps,fault).report_zad_errornow reads those fields, so error annotations surface the cause and the suggested fix. It falls back to the old.errorfield for version skew. Without this, network/unknown failures (HTTP status 0) would have lost their message entirely.Verified locally: shellcheck, actionlint and yamllint pass, and
report_zad_errorwas exercised against real v0.8.0 output for 401, network (status 0), the old flat shape, and non-JSON CLI crashes.