Skip to content

fix(ci): Release workflow failed on every tag whose release already existed #73

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
Thomasbehan merged 1 commit into from
Jul 27, 2026
Merged

fix(ci): Release workflow failed on every tag whose release already existed #73

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
17 changes: 11 additions & 6 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
name: Release

# On a version tag, ensure a GitHub Release exists with generated notes. The trained model
# artifacts (LesNet.M4.5*.keras / .artifacts.json / .tflite) are uploaded to this release by
# the model-build automation (gh release upload) — they are too large to live in the repo/CI.
# On a version tag, ensure a GitHub Release exists. Trained model artifacts (the JEPA family
# tarballs, LesNet.M4.5*.keras / .artifacts.json / .tflite) are uploaded to the release separately
# by the model-build automation (gh release upload) — far too large to live in the repo/CI.
on:
push:
tags:
Expand All @@ -16,12 +16,17 @@ jobs:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Create or update the release
- name: Create the release if it does not already exist
env:
GH_TOKEN: ${{ github.token }}
run: |
# An existing release is left alone: it normally already carries curated notes and
# uploaded model assets, and regenerating notes would silently overwrite them.
# The previous version called `gh release edit --generate-notes`, which is not a valid
# flag for `edit`, so this step failed every time the release already existed.
if gh release view "${GITHUB_REF_NAME}" >/dev/null 2>&1; then
gh release edit "${GITHUB_REF_NAME}" --generate-notes
echo "Release ${GITHUB_REF_NAME} already exists - leaving notes and assets untouched."
else
gh release create "${GITHUB_REF_NAME}" --generate-notes --title "LesNet ${GITHUB_REF_NAME}"
gh release create "${GITHUB_REF_NAME}" \
--generate-notes --title "LesNet ${GITHUB_REF_NAME}"
fi
Loading