Skip to content

ci: add guards for lm eval imports to make importing the metric okay #1245

ci: add guards for lm eval imports to make importing the metric okay

ci: add guards for lm eval imports to make importing the metric okay #1245

Triggered via pull request April 2, 2026 17:08
Status Success
Total duration 2m 23s
Artifacts 1

build.yaml

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

Annotations

1 warning
build (3.11, ubuntu-22.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5, astral-sh/setup-uv@v6. 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
pruna-0.3.2-py3-none-any.whl Expired
348 KB
sha256:8eea8ec288e422106a544226d94bd0d20cf5447d0ca1ec9929bdfa69c2affb7a