Fix workflow typo that is stopping the release of new version #716
Conversation
This file contains 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.
What does this PR do?
Fix workflow typo that is stopping the release of new version.
Details
The workflow got triggered after the merge of PR #711.
However there is a typo that sets the
CREATE_TAGvariable to=trueinstead oftrue, which causes the stepCreate tagto not run:You can see that in this run: https://github.com/elastic/elastic-serverless-forwarder/actions/runs/9079114205/job/24947621376.
How to test this PR locally
It is not possible to test this locally.
Best workaround would be to create your own private repository and create the same environment to make the workflow get triggered.