fix: run release snapshot cleanup after finalize#82
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe workflow file was renamed from Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Code Review
This pull request updates the GitHub workflow tests to reflect the transition from a 'build' to a 'release' workflow, including new validation for the 'cleanup-snapshot-tag' job. Review feedback suggests renaming the test case to accurately describe its expanded scope and adding an assertion to verify that the 'cleanup-snapshot-tag' job explicitly depends on 'build-electron' to ensure the conditional logic is valid.
Summary
Fix the manual release workflow so
cleanup-snapshot-tagcan run after successful finalize builds, and rename the workflow display name frombuildtoreleasewhile keeping the file path asbuild.yml.Why
Fixes #79. In finalize runs,
create-snapshot-tagis intentionally skipped. GitHub Actions can propagate skipped dependencies to downstream jobs unless the downstream job explicitly evaluates its own condition, socleanup-snapshot-tagwas skipped even whenbuild-electronsucceeded. The cleanup job now usesalways()while still requiringphase == finalizeand a successfulbuild-electronresult.Related Issue
Fixes #79
How To Verify
Fresh-eyes review also completed with no Critical, Important, or Minor issues.
Screenshots or Recordings
Not applicable. This is a GitHub Actions workflow change.
Checklist
devbranchSummary by CodeRabbit
Chores
Tests