Skip to content

chore: Revert MultiQC to 1.21 #420

chore: Revert MultiQC to 1.21

chore: Revert MultiQC to 1.21 #420

Triggered via push October 14, 2024 17:23
Status Success
Total duration 12m 27s
Artifacts

ci.yml

on: push
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
test (3, latest-stable, docker)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (1, latest-stable, docker)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (4, latest-stable, docker)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (2, latest-stable, docker)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, mikepenz/action-junit-report@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/