Skip to content

Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 65778cb (main) - autoclosed#230882

Merged
jbudz merged 3 commits intomainfrom
renovate/main-chainguard
Aug 27, 2025
Merged

Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 65778cb (main) - autoclosed#230882
jbudz merged 3 commits intomainfrom
renovate/main-chainguard

Conversation

@elastic-renovate-prod
Copy link
Contributor

@elastic-renovate-prod elastic-renovate-prod bot commented Aug 6, 2025

This PR contains the following updates:

Package Update Change
docker.elastic.co/wolfi/chainguard-base digest 442a566 -> 65778cb

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@elastic-renovate-prod elastic-renovate-prod bot added backport:skip This PR does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:Operations Kibana-Operations Team labels Aug 6, 2025
@elastic-renovate-prod elastic-renovate-prod bot requested a review from a team as a code owner August 6, 2025 21:57
@elastic-renovate-prod elastic-renovate-prod bot added Team:Operations Kibana-Operations Team release_note:skip Skip the PR/issue when compiling release notes backport:skip This PR does not require backporting labels Aug 6, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

1 similar comment
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

@Ikuni17
Copy link
Contributor

Ikuni17 commented Aug 7, 2025

buildkite run renovate helper

@kibanamachine kibanamachine added the ci:cloud-deploy Create or update a Cloud deployment label Aug 7, 2025
@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-chainguard branch from e30c907 to b0fea2c Compare August 8, 2025 06:58
@elastic-renovate-prod elastic-renovate-prod bot changed the title Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 3f07534 (main) Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 0f90ba4 (main) Aug 8, 2025
Ikuni17 added a commit that referenced this pull request Aug 8, 2025
## Summary

Note: I will backport this after backporting the original PR #228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.
@Ikuni17 Ikuni17 added ci:cloud-deploy Create or update a Cloud deployment and removed ci:cloud-deploy Create or update a Cloud deployment labels Aug 8, 2025
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Aug 8, 2025
…231031)

## Summary

Note: I will backport this after backporting the original PR elastic#228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](elastic#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.

(cherry picked from commit f61e1a2)
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Aug 8, 2025
…231031)

## Summary

Note: I will backport this after backporting the original PR elastic#228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](elastic#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.

(cherry picked from commit f61e1a2)
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Aug 8, 2025
…231031)

## Summary

Note: I will backport this after backporting the original PR elastic#228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](elastic#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.

(cherry picked from commit f61e1a2)
Ikuni17 added a commit to Ikuni17/kibana that referenced this pull request Aug 8, 2025
…231031)

## Summary

Note: I will backport this after backporting the original PR elastic#228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](elastic#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.

(cherry picked from commit f61e1a2)

# Conflicts:
#	.buildkite/pull_requests.json
Ikuni17 added a commit to Ikuni17/kibana that referenced this pull request Aug 8, 2025
…231031)

## Summary

Note: I will backport this after backporting the original PR elastic#228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](elastic#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.

(cherry picked from commit f61e1a2)

# Conflicts:
#	.buildkite/pull_requests.json
Ikuni17 added a commit to Ikuni17/kibana that referenced this pull request Aug 8, 2025
…231031)

## Summary

Note: I will backport this after backporting the original PR elastic#228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](elastic#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.

(cherry picked from commit f61e1a2)

# Conflicts:
#	.buildkite/pull_requests.json
Ikuni17 added a commit to Ikuni17/kibana that referenced this pull request Aug 8, 2025
…231031)

## Summary

Note: I will backport this after backporting the original PR elastic#228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](elastic#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.

(cherry picked from commit f61e1a2)

# Conflicts:
#	.buildkite/pull_requests.json
NicholasPeretti pushed a commit to NicholasPeretti/kibana that referenced this pull request Aug 18, 2025
…231031)

## Summary

Note: I will backport this after backporting the original PR elastic#228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](elastic#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.
qn895 pushed a commit to qn895/kibana that referenced this pull request Aug 26, 2025
…231031)

## Summary

Note: I will backport this after backporting the original PR elastic#228664. I
was waiting to see the stability of the original PR.

Fixes two issues:
- The [pipeline](https://buildkite.com/elastic/kibana-renovate-helper)
is not triggering for Renovate PRs, unless explicitly
[commenting](elastic#230882 (comment))
to run
- Since we're passing along `GITHUB_PR_*` env variables to the PR
pipeline. Labels added in the helper pipeline to the PR itself were not
in sync with the PR run. Example [this
run](https://buildkite.com/elastic/kibana-pull-request/builds/327690#019885d3-196a-4950-896c-3bf7de6f735f)
should have `ci:cloud-deploy` label.
@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-chainguard branch from 48d3fd3 to 04ca7cf Compare August 27, 2025 05:49
@elastic-renovate-prod elastic-renovate-prod bot changed the title Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 0f90ba4 (main) Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 4dbe940 (main) Aug 27, 2025
@elastic-renovate-prod elastic-renovate-prod bot force-pushed the renovate/main-chainguard branch from 04ca7cf to 799507b Compare August 27, 2025 13:57
@elastic-renovate-prod elastic-renovate-prod bot changed the title Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 4dbe940 (main) Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 65778cb (main) Aug 27, 2025
@jbudz jbudz added ci:build-cloud-image and removed ci:cloud-deploy Create or update a Cloud deployment labels Aug 27, 2025
@jbudz
Copy link
Contributor

jbudz commented Aug 27, 2025

buildkite test this

@github-actions
Copy link
Contributor

🔍 Preview links for changed docs

@jbudz
Copy link
Contributor

jbudz commented Aug 27, 2025

buildkite test this

@elastic-renovate-prod
Copy link
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

@jbudz jbudz merged commit 6d4fe5a into main Aug 27, 2025
12 checks passed
@jbudz jbudz deleted the renovate/main-chainguard branch August 27, 2025 22:02
@elastic-renovate-prod elastic-renovate-prod bot changed the title Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 65778cb (main) Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 65778cb (main) - autoclosed Aug 27, 2025
qn895 pushed a commit to qn895/kibana that referenced this pull request Sep 2, 2025
…o 65778cb (main) (elastic#230882)

This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| docker.elastic.co/wolfi/chainguard-base | digest | `442a566` ->
`65778cb` |

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Renovate
Bot](https://github.com/renovatebot/renovate).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=-->

---------

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Jon <jon@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting ci:build-cloud-image release_note:skip Skip the PR/issue when compiling release notes Team:Operations Kibana-Operations Team v9.2.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants