Update Prow to v20240805-37a08f946

[poiana]

Multiple distinct gcr.io/k8s-prow/ changes:

Commits	Dates	Images
kubernetes/test-infra@47a381b...a5d9345	2024‑07‑19 → 2024‑07‑31	commenter
kubernetes/test-infra@dbbd2d8...37a08f9	2024‑07‑23 → 2024‑08‑05	branchprotector, checkconfig, clonerefs, crier, deck, entrypoint, ghproxy, hook, horologium, initupload, needs-rebase, peribolos, prow-controller-manager, sidecar, sinker, status-reconciler, tide

/cc

[poiana]

@poiana: GitHub didn't allow me to request PR reviews from the following users: poiana.

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

In response to this:

Multiple distinct gcr.io/k8s-prow/ changes:

Commits	Dates	Images
kubernetes/test-infra@47a381b...a5d9345	2024‑07‑19 → 2024‑07‑31	commenter
kubernetes/test-infra@dbbd2d8...12bb925	2024‑07‑23 → 2024‑07‑30	branchprotector, checkconfig, clonerefs, crier, deck, entrypoint, ghproxy, hook, horologium, initupload, needs-rebase, peribolos, prow-controller-manager, sidecar, sinker, status-reconciler, tide

/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.

[FedeDP]

/approve

[poiana]

LGTM label has been added.

Git tree hash: 2d5cee7832b53a75da3b2eb49cc526c3ee755631

[FedeDP]

/hold

[FedeDP]

/approve

[poiana]

LGTM label has been added.

Git tree hash: fab98a4425cc5185f59bddfffbf47510ac47f246

[poiana]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: FedeDP, poiana

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

The pull request process is described here

Needs approval from an approver in each of these files:

• config/OWNERS [FedeDP]

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

[FedeDP]

/unhold

[poiana]

@poiana: Updated the following 2 configmaps:

• job-config configmap in namespace default at cluster default using the following files:
  • key branchprotector.yaml using file config/jobs/branchprotector/branchprotector.yaml
  • key check-prow-config.yaml using file config/jobs/check-prow-config/check-prow-config.yaml
  • key periodic-close.yaml using file config/jobs/lifecycle-bot/periodic-close.yaml
  • key periodic-rotten.yaml using file config/jobs/lifecycle-bot/periodic-rotten.yaml
  • key periodic-stale.yaml using file config/jobs/lifecycle-bot/periodic-stale.yaml
  • key peribolos.yaml using file config/jobs/peribolos/peribolos.yaml
• config configmap in namespace default at cluster default using the following files:
  • key config.yaml using file config/config.yaml

In response to this:

Multiple distinct gcr.io/k8s-prow/ changes:

Commits	Dates	Images
kubernetes/test-infra@47a381b...a5d9345	2024‑07‑19 → 2024‑07‑31	commenter
kubernetes/test-infra@dbbd2d8...37a08f9	2024‑07‑23 → 2024‑08‑05	branchprotector, checkconfig, clonerefs, crier, deck, entrypoint, ghproxy, hook, horologium, initupload, needs-rebase, peribolos, prow-controller-manager, sidecar, sinker, status-reconciler, tide

/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.