Skip to content

fix: optimize latest release tag retrieval in release.yml #896

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ilopezluna merged 1 commit into from
Apr 30, 2026
Merged

fix: optimize latest release tag retrieval in release.yml #896

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 5 additions & 8 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,14 +63,11 @@ jobs:
BUMP_TYPE: ${{ inputs.bumpType || 'patch' }}
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
# --- Find the latest published GitHub Release tag ---
# Using gh release list instead of git tags ensures we reference the
# last *successfully published* release, not an orphan tag left behind
# by a failed release workflow run.
# - Filter to v* tags only (aligned with the git tag fallback)
# - Use jq's // operator to handle empty arrays (avoids literal "null")
LATEST_RELEASE_TAG=$(gh release list --limit 100 --json tagName \
--jq '[.[] | select(.tagName | startswith("v"))] | sort_by(.tagName) | last | .tagName // ""' \
# --- Find the latest published GitHub Release tag ---
# gh release list defaults to --order desc (newest first by creation
# date), so --limit 1 gives us the most recent release.
LATEST_RELEASE_TAG=$(gh release list --limit 1 --json tagName \
--jq '.[0].tagName // ""' \
2>/dev/null || echo "")

if [ -n "$LATEST_RELEASE_TAG" ]; then
Expand Down
Loading