-
Notifications
You must be signed in to change notification settings - Fork 528
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
[7.17] ci(release): automate release steps for the patch (backport #12273) #12397
Conversation
(cherry picked from commit 1b36392) # Conflicts: # .github/workflows/run-patch-release.yml # release.mk
Requires #12366 |
This pull request has not been merged yet. Could you please review and merge it @v1v? 🙏 |
This PR also contains the changes from #12366 |
This reverts commit dd3f194.
I reverted 9c06696 so I can verify if the And it did work as expected -> https://github.com/elastic/apm-server/actions/runs/7559406648/job/20583139806?pr=12397 |
run elasticsearch-ci/docs |
I'll create a specific PR with the reverted changes in #12397 (comment) |
It used to faile when running the linting, see https://github.com/elastic/apm-server/pull/12397\#issuecomment-1896261419
This is an automatic backport of pull request #12273 done by Mergify.
Cherry-pick of 1b36392 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refresh
will re-evaluate the rules@Mergifyio rebase
will rebase this PR on its base branch@Mergifyio update
will merge the base branch into this PR@Mergifyio backport <destination>
will backport this PR on<destination>
branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com