You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The CI pipeline used to trigger twice per run, once when the branch was pushed, and then again when semantic-release tagged the branch. This required every task in the file to have a conditional to skip if it's the tag. This was required because the pipeline had to get all the way back to the publish task in order for semantic-release to tag the repo, and allowing any task to fail along the way causes the deploy stage needs statement to fail.
Possible Solution
Move publish to separate workflow and mark it on-workflow-call and tags == "v*".
Additional context
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Description
The CI pipeline used to trigger twice per run, once when the branch was pushed, and then again when semantic-release tagged the branch. This required every task in the file to have a conditional to skip if it's the tag. This was required because the pipeline had to get all the way back to the publish task in order for semantic-release to tag the repo, and allowing any task to fail along the way causes the
deploy
stageneeds
statement to fail.Possible Solution
Move
publish
to separate workflow and mark iton-workflow-call
andtags == "v*"
.Additional context
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: