chore(deps): update docker.io/library/ubuntu:24.04 docker digest to d1e2e92 (v1.18)#44476
Merged
cilium-renovate[bot] merged 2 commits intov1.18from Feb 23, 2026
Merged
Conversation
cilium-renovate
bot
added
kind/enhancement
maintainer-s-little-helper
bot
added
backport/1.18
Contributor
Author
|
github-actions
bot
added
the
kind/community-contribution
ciliumbot
approved these changes
Feb 22, 2026
ciliumbot
approved these changes
Feb 22, 2026
ciliumbot
approved these changes
Feb 22, 2026
ciliumbot
requested review from
a team and
brlbil
and removed request for
a team and
brlbil
ciliumbot
approved these changes
Feb 22, 2026
auto-committer
bot
temporarily deployed
to
release-base-images-renovate
ciliumbot
approved these changes
Feb 22, 2026
HadrienPatte
added a commit
that referenced
this pull request
Feb 22, 2026
PR #44389 introduced the `"matchBaseBranches": ["main"]` constraint to the `"disable major/minor k8s updates"` rule. The intent was to scope that rule to main since stable branches would have their own logic, but the new `"k8s.io patch updates stable"` rule only covers patch/digest — it never disables major/minor on stable. So major/minor k8s update fell through with nothing blocking them on v1.17/v1.18/v1.19. That's how we got #44481 attempting to bump those from `v0.32.0` to `v0.35.1` on 1.17 and #44476 from `v0.33.3` to `v0.35.1` on 1.18. This PR removes the `matchBaseBranches: ["main"]` from the disable rule so it applies t all branches. The `"k8s.io patch updates stable"` rule (which explicitly enables patch+digest on stable) will still take precedence for those update types, giving the correct behavior: * All branches: major/minor k8s updates disabled * Stable branches only: patch/digest k8s updates enabled Signed-off-by: Hadrien Patte <[email protected]>
HadrienPatte
added a commit
that referenced
this pull request
Feb 22, 2026
PR #44389 introduced the `"matchBaseBranches": ["main"]` constraint to the `"disable major/minor k8s updates"` rule. The intent was to scope that rule to main since stable branches would have their own logic, but the new `"k8s.io patch updates stable"` rule only covers patch/digest — it never disables major/minor on stable. So major/minor k8s update fell through with nothing blocking them on v1.17/v1.18/v1.19. That's how we got #44481 attempting to bump those from `v0.32.0` to `v0.35.1` on 1.17 and #44476 from `v0.33.3` to `v0.35.1` on 1.18. This PR removes the `matchBaseBranches: ["main"]` from the disable rule so it applies t all branches. The `"k8s.io patch updates stable"` rule (which explicitly enables patch+digest on stable) will still take precedence for those update types, giving the correct behavior: * All branches: major/minor k8s updates disabled * Stable branches only: patch/digest k8s updates enabled Signed-off-by: Hadrien Patte <[email protected]>
HadrienPatte
added a commit
that referenced
this pull request
Feb 22, 2026
PR #44389 introduced the `"matchBaseBranches": ["main"]` constraint to the `"disable major/minor k8s updates"` rule. The intent was to scope that rule to main since stable branches would have their own logic, but the new `"k8s.io patch updates stable"` rule only covers patch/digest — it never disables major/minor on stable. So major/minor k8s update fell through with nothing blocking them on v1.17/v1.18/v1.19. That's how we got #44481 attempting to bump those from `v0.32.0` to `v0.35.1` on 1.17 and #44476 from `v0.33.3` to `v0.35.1` on 1.18. This PR removes the `matchBaseBranches: ["main"]` from the disable rule so it applies t all branches. The `"k8s.io patch updates stable"` rule (which explicitly enables patch+digest on stable) will still take precedence for those update types, giving the correct behavior: * All branches: major/minor k8s updates disabled * Stable branches only: patch/digest k8s updates enabled Signed-off-by: Hadrien Patte <[email protected]>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Feb 23, 2026
PR #44389 introduced the `"matchBaseBranches": ["main"]` constraint to the `"disable major/minor k8s updates"` rule. The intent was to scope that rule to main since stable branches would have their own logic, but the new `"k8s.io patch updates stable"` rule only covers patch/digest — it never disables major/minor on stable. So major/minor k8s update fell through with nothing blocking them on v1.17/v1.18/v1.19. That's how we got #44481 attempting to bump those from `v0.32.0` to `v0.35.1` on 1.17 and #44476 from `v0.33.3` to `v0.35.1` on 1.18. This PR removes the `matchBaseBranches: ["main"]` from the disable rule so it applies t all branches. The `"k8s.io patch updates stable"` rule (which explicitly enables patch+digest on stable) will still take precedence for those update types, giving the correct behavior: * All branches: major/minor k8s updates disabled * Stable branches only: patch/digest k8s updates enabled Signed-off-by: Hadrien Patte <[email protected]>
cilium-renovate
bot
changed the title
cilium-renovate
bot
force-pushed
the
renovate/v1.18-all-dependencies
branch
from
4e93b31 to
2126f94
Compare
cilium-renovate
bot
temporarily deployed
to
release-base-images-renovate
auto-committer
bot
temporarily deployed
to
release-base-images-renovate
…1e2e92 Signed-off-by: cilium-renovate[bot] <134692979+cilium-renovate[bot]@users.noreply.github.com>
cilium-renovate
bot
force-pushed
the
renovate/v1.18-all-dependencies
branch
from
7d8fc31 to
5df013c
Compare
cilium-renovate
bot
temporarily deployed
to
release-base-images-renovate
Signed-off-by: Cilium Imagebot <[email protected]>
auto-committer
bot
temporarily deployed
to
release-base-images-renovate
auto-committer
bot
temporarily deployed
to
Trigger CI from renovate PRs
|
/test |
maintainer-s-little-helper
bot
added
ready-to-merge
fzu-huang
pushed a commit
to fzu-huang/cilium
that referenced
this pull request
Feb 25, 2026
PR cilium#44389 introduced the `"matchBaseBranches": ["main"]` constraint to the `"disable major/minor k8s updates"` rule. The intent was to scope that rule to main since stable branches would have their own logic, but the new `"k8s.io patch updates stable"` rule only covers patch/digest — it never disables major/minor on stable. So major/minor k8s update fell through with nothing blocking them on v1.17/v1.18/v1.19. That's how we got cilium#44481 attempting to bump those from `v0.32.0` to `v0.35.1` on 1.17 and cilium#44476 from `v0.33.3` to `v0.35.1` on 1.18. This PR removes the `matchBaseBranches: ["main"]` from the disable rule so it applies t all branches. The `"k8s.io patch updates stable"` rule (which explicitly enables patch+digest on stable) will still take precedence for those update types, giving the correct behavior: * All branches: major/minor k8s updates disabled * Stable branches only: patch/digest k8s updates enabled Signed-off-by: Hadrien Patte <[email protected]>
javiercardona-work
pushed a commit
to javiercardona-work/cilium
that referenced
this pull request
Mar 18, 2026
PR cilium#44389 introduced the `"matchBaseBranches": ["main"]` constraint to the `"disable major/minor k8s updates"` rule. The intent was to scope that rule to main since stable branches would have their own logic, but the new `"k8s.io patch updates stable"` rule only covers patch/digest — it never disables major/minor on stable. So major/minor k8s update fell through with nothing blocking them on v1.17/v1.18/v1.19. That's how we got cilium#44481 attempting to bump those from `v0.32.0` to `v0.35.1` on 1.17 and cilium#44476 from `v0.33.3` to `v0.35.1` on 1.18. This PR removes the `matchBaseBranches: ["main"]` from the disable rule so it applies t all branches. The `"k8s.io patch updates stable"` rule (which explicitly enables patch+digest on stable) will still take precedence for those update types, giving the correct behavior: * All branches: major/minor k8s updates disabled * Stable branches only: patch/digest k8s updates enabled Signed-off-by: Hadrien Patte <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
cd1dba6→d1e2e92Configuration
📅 Schedule: Branch creation - "on sunday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Never, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.