Fix release workflow: tag regex, artifact validation, and token usage #187
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.
🔧 Summary
This PR improves the release.yml GitHub Actions workflow by addressing several critical issues to ensure consistent and reliable behavior during tag-based releases.
✅ Changes Included
1. Fixed tag trigger regex
Explanation
1-2-3,1_2_3, even1a2b3, which is invalid for versioning.Find attached tested SCREEN SHOT BELOW .
Bad Match with Old Regex:

Proper Match with Fixed Regex:

💬 Note: If you're planning to adopt alternate version tag formats in the future — such as:
v1.0.2 (semantic with prefix)
release-1.0.2 or rel-1.0.2
1.0.2-beta, 1.0.2-rc.1 (prereleases with suffixes)
x1.0.2x (custom wrapping formats)
…feel free to reach out. I'm happy to help extend the workflow to support those formats reliably and safely.
2. Added strict release job guard
3. Explicit artifact validation
action-gh-release.4. Clarified GitHub token usage
@katiewasnothere @wlan0