Skip to content

chore(deps): update docker.elastic.co/wolfi/chainguard-base:latest docker digest to 019627d - #509

Merged
Jan-Kazlouski-elastic merged 1 commit into
mainfrom
renovate/wolfi-versioned
Oct 5, 2026
Merged

Jan-Kazlouski-elastic merged 1 commit into
mainfrom
renovate/wolfi-versioned

Conversation

@elastic-renovate-prod

@elastic-renovate-prod elastic-renovate-prod Bot commented Oct 3, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
docker.elastic.co/wolfi/chainguard-base final digest 7baac74 → 019627d

Configuration

📅 Schedule: Branch creation - Only on Sunday and Saturday ( * * * * 0,6 ) (UTC), 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 requested a review from a team as a code owner October 3, 2026 03:25
@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/wolfi-versioned branch from aea9d28 to 2fb3a63 Compare October 3, 2026 11:24
@elastic-renovate-prod elastic-renovate-prod Bot changed the title chore(deps): update docker.elastic.co/wolfi/chainguard-base:latest docker digest to 707b956 chore(deps): update docker.elastic.co/wolfi/chainguard-base:latest docker digest to 019627d Oct 3, 2026
@Jan-Kazlouski-elastic
Jan-Kazlouski-elastic enabled auto-merge (squash) October 5, 2026 10:37
@Jan-Kazlouski-elastic
Jan-Kazlouski-elastic merged commit f69ea11 into main Oct 5, 2026
2 checks passed
@Jan-Kazlouski-elastic
Jan-Kazlouski-elastic deleted the renovate/wolfi-versioned branch October 5, 2026 10:37
@Jan-Kazlouski-elastic Jan-Kazlouski-elastic self-assigned this Oct 5, 2026
@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown

💔 Failed to create backport PR(s)

The backport operation could not be completed due to the following error:
There are no branches to backport to. Aborting.

The backport PRs will be merged automatically after passing CI.

To backport manually run:
backport --pr 509 --autoMerge --autoMergeMethod squash

@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown

💔 Failed to create backport PR(s)

Status Branch Result
❌ 1.0 Commit could not be cherrypicked due to conflicts
❌ 1.1 Commit could not be cherrypicked due to conflicts

To backport manually run:
backport --pr 509 --autoMerge --autoMergeMethod squash

Jan-Kazlouski-elastic added a commit that referenced this pull request Oct 5, 2026
Brings the `chainguard-base` runtime digest on `1.0` to parity with
`main`: `5a2d51a` → `019627d`.

Renovate only targets `main`, so `1.0` has had no digest bump since #475
(Aug 19) and is nine behind. This PR collapses all of them into one
change — intermediate digests have no standalone meaning and nothing
depends on them.

Covers: #477, #479, #492, #493, #494, #496, #506, #507, #509.

#477 is the carrier because it is the only one whose cherry-pick applies
cleanly onto `1.0`; the rest expect intermediate digests that never
landed here. `Dockerfile.wolfi` is now byte-identical to `main`.

Required before cutting `1.0.1` — otherwise the release image would ship
on a five-month-old base.

---------

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
Co-authored-by: “Jan-Kazlouski-elastic“ <jan.kazlouski@elastic.co>
Jan-Kazlouski-elastic pushed a commit that referenced this pull request Oct 5, 2026
…est docker digest to 019627d (#509) (#515)

Backports the following commits to 1.1:
- chore(deps): update docker.elastic.co/wolfi/chainguard-base:latest
docker digest to 019627d (#509)

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant