Skip to content

Periodically rebuild & publish containers (auto update) #1986

Periodically rebuild & publish containers (auto update)

Periodically rebuild & publish containers (auto update) #1986

Triggered via schedule March 11, 2026 22:43
Status Success
Total duration 1m 33s
Artifacts
Generate jobs
3s
Generate jobs
Matrix: Build & publish container
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Build & publish container (refs/heads/main)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, redhat-actions/podman-login@v1, redhat-actions/push-to-registry@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build & publish container (refs/tags/v2.0.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, redhat-actions/podman-login@v1, redhat-actions/push-to-registry@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/