search

elastic / elastic-agent-shipper

Data shipper for the Elastic Agent - single, unified way to add monitoring for logs, metrics, and other types of data to a host.
Other
9 stars 17 forks source link

[8.7](backport #280) [updatecli][githubrelease] Bump version to 1.19.6 #282

Closed mergify[bot] closed 1 year ago

mergify[bot] commented 1 year ago

This is an automatic backport of pull request #280 done by Mergify.

Mergify commands and options
More conditions and actions can be found in the [documentation](https://docs.mergify.com/). 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 ` will backport this PR on `` branch Additionally, on Mergify [dashboard](https://dashboard.mergify.com/) you can: - look at your merge queues - generate the Mergify configuration with the config editor. Finally, you can contact us on https://mergify.com
cla-checker-service[bot] commented 1 year ago

💚 CLA has been signed

cmacknz commented 1 year ago

@v1v what is causing the CLA check error here for the automated backport commit?

elasticmachine commented 1 year ago

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

#### Build stats * Start Time: 2023-03-07T21:47:20.118+0000 * Duration: 18 min 50 sec

:grey_exclamation: Flaky test report

No test was executed to be analysed.

:robot: GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with: - `/test` : Re-trigger the build.

v1v commented 1 year ago

@v1v what is causing the CLA check error here for the automated backport commit?

IIUC, it should not happen, let me see if I can find how the CLA works

v1v commented 1 year ago

I understand now, the original PR was committed by GitHub Actions - Bot https://github.com/elastic/elastic-agent-shipper/pull/280 and it's not granted. Let me approve it.

This should not happen anymore in the future, as we are not gonna use the github actions-bot user but one of our automated accounts (I'm working on it now)