Repository navigation
ci: warn instead of notice when a release tag is skipped - #27
Merged
Merged
Conversation
A malformed release tag is a typo, not an expected state. ::notice:: made that path effectively silent, so the major tag would quietly fail to move. Surface it as a warning instead. This was pushed to #26 just after it merged, so it missed the merge. Applying it here keeps this file identical to the copies now proposed for the four sibling action repos.
![orca-security-eu[bot]](https://avatars.githubusercontent.com/in/276244?s=60&v=4){kind=small}
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
 Passed |
Secrets |  0  0  0  0 |
View in Orca |
| Passed |
Vulnerabilities | 0 0 0 0 |
View in Orca |
|
guydanko-orca
approved these changes
Nov 8, 2026
guydanko-orca
left a comment
guydanko-orca
left a comment
There was a problem hiding this comment.
LGTM. Matches the workflow merged in #26.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Follow-up to #26 — this one-line change was pushed to that branch moments after it merged, so it missed the merge.
A malformed release tag (the
v.1.0.2in this repo's history, or thev.1.5.12currently latest in shiftleft-iac-action) is a typo, not an expected state. With::notice::the skip path was effectively silent: the major tag would quietly fail to move and the run would still be green. A warning puts it in the run summary.Also keeps this file byte-identical to the copies proposed for the four sibling repos, so the five don't start drifting from each other on day one: