Skip to content

Implement access request link expiration setting #3789

Implement access request link expiration setting

Implement access request link expiration setting #3789

Triggered via pull request August 10, 2023 16:06
Status Success
Total duration 29m 30s
Artifacts

tests.yml

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

Annotations

24 warnings
Tests (3.8, pypi, postgresql13, elasticsearch7, 16.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests (3.8, pypi, postgresql13, elasticsearch7, 16.x): invenio_rdm_records/assets/semantic-ui/js/invenio_rdm_records/src/deposit/fields/ReferencesField/ReferencesField.js#L23
Fragments should contain more than one child - otherwise, there’s no need for a Fragment at all
Tests (3.8, pypi, postgresql13, opensearch2, 16.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests (3.8, pypi, postgresql13, opensearch2, 16.x): invenio_rdm_records/assets/semantic-ui/js/invenio_rdm_records/src/deposit/fields/ReferencesField/ReferencesField.js#L23
Fragments should contain more than one child - otherwise, there’s no need for a Fragment at all
Tests (3.7, pypi, postgresql13, elasticsearch7, 16.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests (3.7, pypi, postgresql13, elasticsearch7, 16.x): invenio_rdm_records/assets/semantic-ui/js/invenio_rdm_records/src/deposit/fields/ReferencesField/ReferencesField.js#L23
Fragments should contain more than one child - otherwise, there’s no need for a Fragment at all
Tests (3.7, pypi, postgresql13, opensearch2, 16.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests (3.7, pypi, postgresql13, opensearch2, 16.x): invenio_rdm_records/assets/semantic-ui/js/invenio_rdm_records/src/deposit/fields/ReferencesField/ReferencesField.js#L23
Fragments should contain more than one child - otherwise, there’s no need for a Fragment at all
Tests (3.9, pypi, postgresql13, elasticsearch7, 16.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests (3.9, pypi, postgresql13, elasticsearch7, 16.x): invenio_rdm_records/assets/semantic-ui/js/invenio_rdm_records/src/deposit/fields/ReferencesField/ReferencesField.js#L23
Fragments should contain more than one child - otherwise, there’s no need for a Fragment at all
Tests (3.9, pypi, postgresql13, opensearch2, 16.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests (3.9, pypi, postgresql13, opensearch2, 16.x): invenio_rdm_records/assets/semantic-ui/js/invenio_rdm_records/src/deposit/fields/ReferencesField/ReferencesField.js#L23
Fragments should contain more than one child - otherwise, there’s no need for a Fragment at all