Skip to content

rcx-tk: 0.1.0 → 0.2.0, rename metadata→sequence, add msdial corrections tool #2168

rcx-tk: 0.1.0 → 0.2.0, rename metadata→sequence, add msdial corrections tool

rcx-tk: 0.1.0 → 0.2.0, rename metadata→sequence, add msdial corrections tool #2168

Triggered via pull request March 11, 2026 11:27
Status Cancelled
Total duration 4m 33s
Artifacts

pr.yaml

on: pull_request
Matrix: Setup cache and determine changed repositories
Matrix: Lint tool-list
Matrix: Lint Python scripts
Matrix: Lint R scripts
Matrix: Test tools
Check file sizes
0s
Check file sizes
Matrix: Combine chunked test results
Matrix: Deploy
Check workflow success
2s
Check workflow success
Report deploy status
0s
Report deploy status
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 1 warning
Setup cache and determine changed repositories (3.11)
Canceling since a higher priority waiting request for pr-refs/pull/737/merge exists
Setup cache and determine changed repositories (3.11)
The operation was canceled.
Check workflow success
Process completed with exit code 1.
Galaxy Tool Linting and Tests for push and PR
Canceling since a higher priority waiting request for pr-refs/pull/737/merge exists
Setup cache and determine changed repositories (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/