Skip to content

chore(deps): update actions/setup-python action to v5.6.0 #445

chore(deps): update actions/setup-python action to v5.6.0

chore(deps): update actions/setup-python action to v5.6.0 #445

Triggered via pull request April 3, 2026 04:51
Status Success
Total duration 1m 3s
Artifacts 1

linting.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

19 errors and 2 warnings
Test Process PLOT_RUN_GANTT.Should run without failures: Test Process PLOT_RUN_GANTT#L1
Assertion failed: 2 of 2 assertions failed
Test Process SEQERA_RUNS_DUMP.Should run without failures: Test Process SEQERA_RUNS_DUMP#L1
java.lang.RuntimeException: Process has no output channels. process.out can not be used.
Test pipeline.-profile test: Test pipeline#L1
Assertion failed: 2 of 2 assertions failed
Test pipeline.-profile test_benchmark: Test pipeline#L1
Assertion failed: 2 of 2 assertions failed
Test Process BENCHMARK_REPORT.Should run with removing failed tasks: Test Process BENCHMARK_REPORT#L1
Assertion failed: assert process.success | | | false BENCHMARK_REPORT
Test Functions.Test Function getWorkflowVersion: Test Functions#L1
Assertion failed: 2 of 2 assertions failed
Test Functions.Test Function dumpParametersToJSON: Test Functions#L1
Assertion failed: 1 of 1 assertions failed
Test Functions.Test Function checkCondaChannels: Test Functions#L1
Assertion failed: 1 of 2 assertions failed
Test Process MULTIQC.sarscov2 single-end [fastqc]: Test Process MULTIQC#L1
Assertion failed: 4 of 4 assertions failed
Test Process MULTIQC.sarscov2 single-end [fastqc] [config]: Test Process MULTIQC#L1
Assertion failed: 4 of 4 assertions failed
Test Process MULTIQC.sarscov2 single-end [fastqc] - stub: Test Process MULTIQC#L1
Assertion failed: 2 of 2 assertions failed
pre-commit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@0ad4b8fadaa221de15dcec353f45205ec38ea70b, actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065. 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/
nf-core
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./setup-nextflow/subaction, actions/checkout@0ad4b8fadaa221de15dcec353f45205ec38ea70b, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-java@8df1039502a15bceb9433410b1a100fbe190c53b, actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065, actions/upload-artifact@65462800fd760344b1a7b4382951275a0abb4808, pietrobolcato/action-read-yaml@1.1.0. 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
linting-logs Expired
6.53 KB
sha256:e0facac6564c31e42730595c1ae68a641f0e95cedf7a772838398c1867c14ea8