Skip to content

legacy: fix legacy files api when published #918

legacy: fix legacy files api when published

legacy: fix legacy files api when published #918

Triggered via pull request September 18, 2023 20:34
Status Failure
Total duration 7m 28s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

tests.yml

on: pull_request
Matrix: Tests
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
Tests (site, 3.9, postgresql14, opensearch2, false)
Process completed with exit code 1.
Tests (legacy, 3.9, postgresql14, opensearch2, false)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests (migrator, true, 3.9, postgresql14)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests (site, 3.9, postgresql14, opensearch2, false)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/