Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[MEDIUM] Moving job-level
ifskips artifact verification steps on non-tag pushesPreviously the
if: startsWith(github.ref, 'refs/tags/v')guard was only on the finalncipollo/release-actionstep. That meant on every push tomain(non-tag), the job still ran:actions/download-artifact— fetches the release artifacttree -nh ./bin/release— lists artifactsfind bin/release -type f -exec file …— checks binary types…but skipped only the actual GitHub Release creation. These steps acted as a post-build artifact sanity check for every push.
After this PR, the entire
releasejob is skipped on non-tag pushes, so those sanity checks no longer run onmainbranch pushes. If this is intentional (just avoiding unnecessary work), the PR description doesn't mention it and it's worth a comment to confirm. If the artifact verification was considered useful, consider keeping those steps outside the tag guard: