chore(deps): bump the github-actions-dependencies group across 10 directories with 11 updates #736
neilime__pull-request-ci.yml
on: pull_request
Matrix: ci / linter / 🛡️ CodeQL Analysis
ci
/
...
/
🧹 Lint Code Base
1m 55s
ci
/
...
/
prepare-actions-linting
9s
ci
/
...
/
📦 Prepare configuration
2s
ci
/
...
/
📦 Prepare configuration
5s
ci
/
...
/
prepare-variables
3s
ci
/
...
/
🛡️ CodeQL Analysis
59s
ci
/
...
/
🛡️ Dependency Review
56s
ci
/
...
/
🛡️ CodeQL Analysis
1m 1s
ci
/
...
/
🛡️ Dependency Review
1m 13s
Matrix: ci / Test action "dependencies-cache" / test
Matrix: ci / Test action "get-package-manager" / test
Matrix: ci / Test action "has-installed-dependencies" / test
Matrix: ci / Test action "package" / test
Matrix: ci / Test action "setup-node" / test
ci
/
...
/
⚙️ Setup
7s
ci
/
...
/
⚙️ Setup
5s
Matrix: ci / Test workflow "continuous-integration" / Arrange - Build container image for CI workflow / build-images
ci
/
...
/
🏗️ Build
51s
ci
/
...
/
👕 Lint
54s
ci
/
...
/
🏗️ Build
47s
ci
/
...
/
👕 Lint
57s
ci
/
...
/
Publish images manifests
27s
ci
/
...
/
🧪 Test
1m 17s
ci
/
...
/
🧪 Test
1m 8s
ci
/
...
/
📦 Prepare configuration
2s
ci
/
...
/
📦 Prepare configuration
5s
ci
/
...
/
🛡️ CodeQL Analysis
1m 3s
ci
/
...
/
🛡️ Dependency Review
58s
ci
/
...
/
🛡️ CodeQL Analysis
1m 0s
ci
/
...
/
🛡️ Dependency Review
56s
ci
/
...
/
Assert - Ensure build artifact has been uploaded (without container)
8s
ci
/
...
/
⚙️ Setup
31s
ci
/
...
/
⚙️ Setup
32s
ci
/
...
/
🏗️ Build
41s
ci
/
...
/
👕 Lint
53s
ci
/
...
/
🏗️ Build
41s
ci
/
...
/
👕 Lint
54s
ci
/
...
/
🧪 Test
1m 0s
ci
/
...
/
🧪 Test
1m 0s
ci
/
...
/
Assert - Ensure build artifact has been uploaded (with container advanced)
4s
ci
/
...
/
Assert - Ensure build artifact has been uploaded (with container)
4s
Annotations
72 warnings
|
ci / linter / 🛡️ CodeQL Analysis (actions)
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.
|
|
ci / linter / 🛡️ CodeQL Analysis (actions)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (without container) / 🛡️ Dependency Review
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/dependency-review-action@2031cfc080254a8a887f58cffee85186f0e49e48. 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/
|
|
OpenSSF Scorecard Warning
npm/regenerate-unicode-properties has an OpenSSF Scorecard of 2.9, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/ordered-binary has an OpenSSF Scorecard of 2, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/http-cache-semantics has an OpenSSF Scorecard of 2.1, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/generator-function has an OpenSSF Scorecard of 2.8, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/end-of-stream has an OpenSSF Scorecard of 2.5, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/cookie-signature has an OpenSSF Scorecard of 2.3, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/anser has an OpenSSF Scorecard of 2.1, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/@lezer/lr has an OpenSSF Scorecard of 2.1, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/@lezer/common has an OpenSSF Scorecard of 2.6, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/@expo/devcert has an OpenSSF Scorecard of 2.2, which is less than this repository's threshold of 3.
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (without container) / 🛡️ CodeQL Analysis
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.
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (without container) / 🛡️ CodeQL Analysis
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (without container and GitHub reports) / 🛡️ CodeQL Analysis
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.
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (without container and GitHub reports) / 🛡️ CodeQL Analysis
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
|
ci / Test workflow "continuous-integration" / Arrange - Build container image for CI workflow / Build image ci-npm for linux/amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd, int128/docker-build-cache-config-action@4788c7e22b9923ca0e44bc7a29281b5beb545e5d, reproducible-containers/buildkit-cache-dance@1b8ab18fbda5ad3646e3fcc9ed9dd41ce2f297b4. 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/
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (without container and GitHub reports) / 🛡️ Dependency Review
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/dependency-review-action@2031cfc080254a8a887f58cffee85186f0e49e48. 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/
|
|
OpenSSF Scorecard Warning
npm/regenerate-unicode-properties has an OpenSSF Scorecard of 2.9, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/ordered-binary has an OpenSSF Scorecard of 2, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/http-cache-semantics has an OpenSSF Scorecard of 2.1, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/generator-function has an OpenSSF Scorecard of 2.8, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/end-of-stream has an OpenSSF Scorecard of 2.5, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/cookie-signature has an OpenSSF Scorecard of 2.3, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/anser has an OpenSSF Scorecard of 2.1, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/@lezer/lr has an OpenSSF Scorecard of 2.1, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/@lezer/common has an OpenSSF Scorecard of 2.6, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/@expo/devcert has an OpenSSF Scorecard of 2.2, which is less than this repository's threshold of 3.
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (without container) / 🏗️ Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (without container and GitHub reports) / 🏗️ Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (without container and GitHub reports) / 👕 Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (without container) / 👕 Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
|
|
ci / Test workflow "continuous-integration" / Arrange - Build container image for CI workflow / Publish images manifests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (without container) / 🧪 Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (with container and advanced options) / 🛡️ Dependency Review
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/dependency-review-action@2031cfc080254a8a887f58cffee85186f0e49e48. 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/
|
|
OpenSSF Scorecard Warning
npm/regenerate-unicode-properties has an OpenSSF Scorecard of 2.9, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/ordered-binary has an OpenSSF Scorecard of 2, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/http-cache-semantics has an OpenSSF Scorecard of 2.1, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/generator-function has an OpenSSF Scorecard of 2.8, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/end-of-stream has an OpenSSF Scorecard of 2.5, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/cookie-signature has an OpenSSF Scorecard of 2.3, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/anser has an OpenSSF Scorecard of 2.1, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/@lezer/lr has an OpenSSF Scorecard of 2.1, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/@lezer/common has an OpenSSF Scorecard of 2.6, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/@expo/devcert has an OpenSSF Scorecard of 2.2, which is less than this repository's threshold of 3.
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (with container) / 🛡️ Dependency Review
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/dependency-review-action@2031cfc080254a8a887f58cffee85186f0e49e48. 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/
|
|
OpenSSF Scorecard Warning
npm/regenerate-unicode-properties has an OpenSSF Scorecard of 2.9, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/ordered-binary has an OpenSSF Scorecard of 2, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/http-cache-semantics has an OpenSSF Scorecard of 2.1, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/generator-function has an OpenSSF Scorecard of 2.8, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/end-of-stream has an OpenSSF Scorecard of 2.5, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/cookie-signature has an OpenSSF Scorecard of 2.3, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/anser has an OpenSSF Scorecard of 2.1, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/@lezer/lr has an OpenSSF Scorecard of 2.1, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/@lezer/common has an OpenSSF Scorecard of 2.6, which is less than this repository's threshold of 3.
|
|
OpenSSF Scorecard Warning
npm/@expo/devcert has an OpenSSF Scorecard of 2.2, which is less than this repository's threshold of 3.
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (with container and advanced options) / 🛡️ CodeQL Analysis
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.
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (with container and advanced options) / 🛡️ CodeQL Analysis
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (with container) / 🛡️ CodeQL Analysis
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.
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (with container) / 🛡️ CodeQL Analysis
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (without container and GitHub reports) / 🧪 Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (with container and advanced options) / 🏗️ Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (with container) / 🏗️ Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (with container and advanced options) / 👕 Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (with container) / 👕 Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (with container and advanced options) / 🧪 Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
|
ci / Test workflow "continuous-integration" / Act - Run the continuous integration workflow (with container) / 🧪 Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ChristopherHX/oidc@73eee1ff03fdfce10eda179f617131532209edbd. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
hoverkraft-tech~ci-github-nodejs~XC17SE.dockerbuild
|
44.3 KB |
sha256:b778805e541c936224805ef7848f57de7c08df22d75b269f74aa583feaa1ecb6
|
|
|
setup-build-24364460564-frvzmz
|
275 Bytes |
sha256:63a5ec19ad48e74ecda14c3a25607fe3cb26fefe4ae74c4840ff8ab7b3758d2e
|
|
|
setup-build-24364460564-mwfw8c
|
177 Bytes |
sha256:e4af18b464e928de3fb3bff681b25001f1b8b99b6381c5a217a46d1be05cea62
|
|
|
setup-build-24364460564-q53c9e
|
275 Bytes |
sha256:63a5ec19ad48e74ecda14c3a25607fe3cb26fefe4ae74c4840ff8ab7b3758d2e
|
|
|
setup-build-24364460564-u8ciif
|
177 Bytes |
sha256:83c5ba5fe93f496da0126b85ec215e8e2c7985277fe5a0fa3a88fbd10fb116d9
|
|
|
test-for-ci-with-npm-0.1.0.tgz
|
856 Bytes |
sha256:0a14282d8d5cdaa88f2cb9cd1e57ca750acddc7880579214b22ae59fe0d55823
|
|
|
test-for-ci-with-pnpm-0.1.0.tgz
|
785 Bytes |
sha256:fad0ad8fee5c388113a8cf284a4134e4346f26956da04308d21eebc25c5e9c86
|
|
|
test-for-ci-with-pnpm-in-package-json-0.1.0.tgz
|
806 Bytes |
sha256:22739902199f1801e9cc3b6d2742248021ad99e533b092c1c4e65cb3cd4fbbfe
|
|
|
test-for-ci-with-yarn-0.1.0.tgz
|
312 Bytes |
sha256:f8d6356b41ba48ef2189dccd2372811e35408626394fd40bb4b4b266890a3c69
|
|