-
Notifications
You must be signed in to change notification settings - Fork 3.5k
TEST: use stub GH action workflow to test new LS version action [NOT FOR MERGE] #18050
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
|
This pull request does not have a backport label. Could you fix it @donoghuc? 🙏
|
|
|
1 similar comment
|
|
|
|
1 similar comment
|
|
68d599f to
972aed3
Compare
|
|
2 similar comments
|
|
|
|
This commit adds a GH action for bumping the logstash version. It uses the updatescli based on a suggestion for how the beats team is doing file updates. There is a workflow_dispatch trigger that accepts a new logstash version. Both the versions.yml and lock file are updated. If it is a branch where we are not vendoring a lockfile that file is skipped without failing the workflow step.
use pattern suggested in code review
1051c59 to
b7bf644
Compare
b7bf644 to
d53ef1d
Compare
|
|
|
|
|
|
|
|
|
💛 Build succeeded, but was flaky
Failed CI StepsHistory
|
|
|





TEST: use stub GH action workflow to test action
This PR is not meant to be merged. It is for demonstrating a successful action run for #18035