Skip to content

Added missing material to README.md. Uncommented a line in docker-co… #212

Added missing material to README.md. Uncommented a line in docker-co…

Added missing material to README.md. Uncommented a line in docker-co… #212

Triggered via push March 14, 2026 14:52
Status Success
Total duration 3m 19s
Artifacts

latest.yml

on: push
maven-snapshot  /  deploy
1m 30s
maven-snapshot / deploy
docker-latest  /  check-commit-message
3s
docker-latest / check-commit-message
docker-latest  /  build-context
3s
docker-latest / build-context
docker-latest  /  publish-image
1m 36s
docker-latest / publish-image
Matrix: docker-latest-multi-arch / Docker Build
Waiting for pending jobs
trigger-deployment
5s
trigger-deployment
docker-latest-multi-arch  /  Docker Publish
docker-latest-multi-arch / Docker Publish
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
maven-snapshot / deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, hashicorp/vault-action@v3. 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/
docker-latest / 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. 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-latest / 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. 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/
trigger-deployment
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v6. 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/