From 2e6305ca8555c4207a5648b028b8b7d870a4120b Mon Sep 17 00:00:00 2001 From: krisztianfekete Date: Thu, 5 Nov 2026 14:45:56 +0100 Subject: [PATCH] fix(ci): check the highest kagent version tag instead of the GitHub latest release --- .github/workflows/kagent-contract.yml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/.github/workflows/kagent-contract.yml b/.github/workflows/kagent-contract.yml index 31dcc76..d9685e1 100644 --- a/.github/workflows/kagent-contract.yml +++ b/.github/workflows/kagent-contract.yml @@ -38,11 +38,13 @@ jobs: # The release tag is fetched and used in one step, and check.sh validates it # before use, so nothing fetched passes through GITHUB_ENV or an expression. + # The newest release is the highest version tag, not GitHub's "Latest" flag, + # which a patch to an older line can take (v0.10.x has no telemetry registry). + # versionsort.suffix sorts v1.0.0-rc2 before v1.0.0. - name: Check kagent main and the newest release - env: - GH_TOKEN: ${{ github.token }} run: | - release="$(gh release view --repo kagent-dev/kagent --json tagName --jq .tagName)" + release="$(git -c versionsort.suffix=- ls-remote --tags --refs --sort=version:refname \ + https://github.com/kagent-dev/kagent.git 'refs/tags/v*' | tail -n 1 | sed 's#.*refs/tags/##')" tests/contract/kagent/check.sh report.md main "$release" - name: Summarize