Skip to content

Upgrade: Bump the dependencies group across 1 directory with 4 updates #443

Upgrade: Bump the dependencies group across 1 directory with 4 updates

Upgrade: Bump the dependencies group across 1 directory with 4 updates #443

Triggered via pull request April 1, 2026 15:03
Status Success
Total duration 1m 27s
Artifacts 2

testing.yml

on: pull_request
Matrix: Testing / Build / build
Testing  /  ...  /  Flake8
8s
Testing / Flake8 / Flake8
Testing  /  ...  /  Black
6s
Testing / Black / Black
Testing  /  ...  /  Security and Quality
1m 20s
Testing / CodeQL / Security and Quality
Testing  /  ...  /  Publish image
Testing / Build / Publish image
Testing  /  Annotation Check
4s
Testing / Annotation Check
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Testing / Build / Build (linux/amd64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/metadata-action@v5, docker/setup-buildx-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/
Testing / Build / Build (linux/arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/metadata-action@v5, docker/setup-buildx-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/
Testing / Annotation Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: OpenTTD/actions/annotation-check@v5. 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/
Testing / CodeQL / Security and Quality
Starting April 2026, the CodeQL Action will skip computing file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. To opt out of this change, set the `CODEQL_ACTION_FILE_COVERAGE_ON_PRS` environment variable to `true`. Alternatively, create a custom repository property with the name `github-codeql-file-coverage-on-prs` and the type "True/false", then set this property to `true` in the repository's settings.

Artifacts

Produced during runtime
Name Size Digest
OpenTTD~eints~TK6GVQ.dockerbuild
65.5 KB
sha256:5f46287c97a881f7b4e3272f6b23bf1c9efc182655a6e367ee61a44bec17806a
OpenTTD~eints~U30DH5.dockerbuild
64.3 KB
sha256:c4635bf4343d5173a2276793ab847372237082e316ff6094e3810a90a8041dab