Skip to content

Add separate pipeline to check output against compliance-checker #1

Add separate pipeline to check output against compliance-checker

Add separate pipeline to check output against compliance-checker #1

Triggered via pull request April 14, 2026 12:18
Status Cancelled
Total duration 57s
Artifacts

compliance_check.yml

on: pull_request
compliance-checker
55s
compliance-checker
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
compliance-checker
Canceling since a higher priority waiting request for compliance_check-refs/pull/39/merge exists
compliance-checker
The operation was canceled.
compliance_check
Canceling since a higher priority waiting request for compliance_check-refs/pull/39/merge exists
compliance-checker
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, conda-incubator/setup-miniconda@v3. 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/
compliance-checker
The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
compliance-checker
`auto-activate-base` is deprecated. Please use `auto-activate`. If your installer does not use the `base` environment as the default environment, also add `activate-environment: base`.