Skip to content

Update examples

Update examples #98

Triggered via push May 14, 2026 19:17
Status Success
Total duration 1m 43s
Artifacts
docker-release  /  check-commit-message
2s
docker-release / check-commit-message
docker-release  /  build-context
5s
docker-release / build-context
docker-release  /  publish-image
1m 37s
docker-release / publish-image
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
docker-release / build-context
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: danubetech/github-action-log-build-context@v0.1.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
docker-release / publish-image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hashicorp/vault-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/