Skip to content

Conversation

@knative-prow-updater-robot
Copy link
Contributor

@knative-prow-updater-robot knative-prow-updater-robot commented Dec 29, 2025

Multiple distinct us-docker.pkg.dev/k8s-infra-prow/images/ changes:

Commits Dates Images
kubernetes-sigs/prow@6bd26c8...782d8a7 2025‑12‑18 → 2026‑01‑12 images/branchprotector, images/checkconfig, images/cherrypicker, images/clonerefs, images/config-bootstrapper, images/crier, images/deck, images/entrypoint, images/generic-autobumper, images/ghproxy, images/hook, images/horologium, images/initupload, images/mkpj, images/needs-rebase, images/peribolos, images/prow-controller-manager, images/sidecar, images/sinker, images/status-reconciler, images/tide

Multiple distinct gcr.io/k8s-staging-boskos/ changes:

Commits Dates Images
kubernetes-sigs/boskos@e3340a3...c2c6f43 2025‑12‑18 → 2026‑01‑07 boskos, janitor, reaper

/cc

@knative-prow-updater-robot knative-prow-updater-robot added the skip-review The PR merges when the automated tests pass, without human review label Dec 29, 2025
@knative-prow
Copy link

knative-prow bot commented Dec 29, 2025

@knative-prow-updater-robot: GitHub didn't allow me to request PR reviews from the following users: knative-prow-updater-robot.

Note that only knative members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

Multiple distinct us-docker.pkg.dev/k8s-infra-prow/images/ changes:

Commits Dates Images
kubernetes-sigs/prow@6bd26c8...f0341d7 2025‑12‑18 → 2025‑12‑23 images/branchprotector, images/checkconfig, images/cherrypicker, images/clonerefs, images/config-bootstrapper, images/crier, images/deck, images/entrypoint, images/generic-autobumper, images/ghproxy, images/hook, images/horologium, images/initupload, images/mkpj, images/needs-rebase, images/peribolos, images/prow-controller-manager, images/sidecar, images/sinker, images/status-reconciler, images/tide

No gcr.io/k8s-staging-boskos/ changes.

/cc

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@knative-prow knative-prow bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Dec 29, 2025
@knative-prow
Copy link

knative-prow bot commented Dec 29, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: knative-prow-updater-robot
Once this PR has been reviewed and has the lgtm label, please assign upodroid for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Multiple distinct us-docker.pkg.dev/k8s-infra-prow/images/ changes:

Commits | Dates | Images
--- | --- | ---
kubernetes-sigs/prow@6bd26c8...782d8a7 | 2025‑12‑18 → 2026‑01‑12 | images/branchprotector, images/checkconfig, images/cherrypicker, images/clonerefs, images/config-bootstrapper, images/crier, images/deck, images/entrypoint, images/generic-autobumper, images/ghproxy, images/hook, images/horologium, images/initupload, images/mkpj, images/needs-rebase, images/peribolos, images/prow-controller-manager, images/sidecar, images/sinker, images/status-reconciler, images/tide

Multiple distinct gcr.io/k8s-staging-boskos/ changes:

Commits | Dates | Images
--- | --- | ---
kubernetes-sigs/boskos@e3340a3...c2c6f43 | 2025‑12‑18 → 2026‑01‑07 | boskos, janitor, reaper
@knative-prow-updater-robot knative-prow-updater-robot changed the title Update Prow to v20251223-f0341d7b5 Update Prow to v20260112-782d8a7cf, Boskos to v20260107-c2c6f43 Jan 12, 2026
@knative-prow knative-prow bot merged commit 9ca25b7 into knative:main Jan 12, 2026
17 checks passed
@knative-prow
Copy link

knative-prow bot commented Jan 12, 2026

@knative-prow-updater-robot: Updated the following 2 configmaps:

  • config configmap in namespace default at cluster default using the following files:
    • key config.yaml using file prow/config.yaml
  • job-config configmap in namespace default at cluster default using the following files:
    • key autobump-flaky-test-reporter.yaml using file prow/jobs/custom/autobump-flaky-test-reporter.yaml
    • key autobump-prow-tests.yaml using file prow/jobs/custom/autobump-prow-tests.yaml
    • key autobump-prow.yaml using file prow/jobs/custom/autobump-prow.yaml
    • key autodeploy-prow.yaml using file prow/jobs/custom/autodeploy-prow.yaml
    • key branchprotector.yaml using file prow/jobs/custom/branchprotector.yaml
    • key infra.yaml using file prow/jobs/custom/infra.yaml
    • key peribolos.yaml using file prow/jobs/custom/peribolos.yaml
Details

In response to this:

Multiple distinct us-docker.pkg.dev/k8s-infra-prow/images/ changes:

Commits Dates Images
kubernetes-sigs/prow@6bd26c8...782d8a7 2025‑12‑18 → 2026‑01‑12 images/branchprotector, images/checkconfig, images/cherrypicker, images/clonerefs, images/config-bootstrapper, images/crier, images/deck, images/entrypoint, images/generic-autobumper, images/ghproxy, images/hook, images/horologium, images/initupload, images/mkpj, images/needs-rebase, images/peribolos, images/prow-controller-manager, images/sidecar, images/sinker, images/status-reconciler, images/tide

Multiple distinct gcr.io/k8s-staging-boskos/ changes:

Commits Dates Images
kubernetes-sigs/boskos@e3340a3...c2c6f43 2025‑12‑18 → 2026‑01‑07 boskos, janitor, reaper

/cc

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/M Denotes a PR that changes 30-99 lines, ignoring generated files. skip-review The PR merges when the automated tests pass, without human review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant