build

Merge branch 'upstream-v334' into upgrade-to-upstream-3-3-4 #35

Sign in to view logs

Triggered via push October 22, 2024 12:08

upgrade-to-upstream-3-3-4

Status Failure

Total duration 1m 35s

Artifacts –

build.yml

on: push

Matrix: build

Annotations

2 errors and 4 warnings

build (3.0, gemfiles/activerecord61.gemfile, 12)

Process completed with exit code 1.

build (2.7, gemfiles/activerecord60.gemfile, 10)

Process completed with exit code 1.

build (3.0, gemfiles/activerecord61.gemfile, 12)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

build (3.1, Gemfile, 15)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

build (3.2, gemfiles/activerecord71.gemfile, 16)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

build (2.7, gemfiles/activerecord60.gemfile, 10)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/