Repository navigation
fix(ci): check the highest kagent version tag instead of the GitHub latest release - #274
Merged
Merged
Conversation
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.
The daily kagent contract check (#273) failed because it checked whichever release GitHub flags as "Latest". kagent published v0.10.5, a patch for its older line, after v1.0.0-rc2, so v0.10.5 took the flag. The 0.10 line has no
telemetry/registry, so Weaver could not find the registry.The check now takes the highest version tag from
git ls-remotewithversionsort.suffix=-, so prereleases sort before their final release. This drops the GitHub API call andGH_TOKENfrom that step.Verified locally: the step picks
v1.0.0-rc2, andcheck.sh report.md main v1.0.0-rc2passes.