fix(ci): avoid failing release job when tag already exists#145
fix(ci): avoid failing release job when tag already exists#145JerrettDavis merged 1 commit intomainfrom
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Snapshot WarningsEnsure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice. Scanned FilesNone |
Test Results417 tests 417 ✅ 1m 29s ⏱️ Results for commit 776c658. |
🔍 PR Validation ResultsVersion: `` ✅ Validation Steps
📊 ArtifactsDry-run artifacts have been uploaded and will be available for 7 days. This comment was automatically generated by the PR validation workflow. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #145 +/- ##
==========================================
+ Coverage 81.14% 81.18% +0.03%
==========================================
Files 196 196
Lines 19134 19134
Branches 2712 2712
==========================================
+ Hits 15527 15533 +6
+ Misses 2880 2879 -1
+ Partials 727 722 -5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
1 participant
Problem\nRelease job in CI was failing on main when � already existed remotely.\n\nThe workflow used git rev-parse (local check), which can miss remote-only tags and still attempt git push origin vX, causing a hard failure.\n\n## Fix\n- switch tag existence check to remote source of truth: git ls-remote --tags origin refs/tags/\n- skip tag push when tag exists on origin\n\n## Why this helps\nThis prevents the release workflow from failing just because the tag already exists, keeping CI/CD green and idempotent for repeated runs on the same package version.