Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-rs/cargo@v1, actions/checkout@v4, actions/setup-python@v5, astral-sh/setup-uv@v5. 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/

be sure to add `/home/runner/work/OpenSK/OpenSK/OpenSK_base/third_party/wasefire/.root/bin` to your PATH to be able to run the installed binaries

package `libc v0.2.154` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked

default toolchain implicitly overridden with `nightly-2026-04-01-x86_64-unknown-linux-gnu` by environment variable

be sure to add `/home/runner/work/OpenSK/OpenSK/third_party/wasefire/.root/bin` to your PATH to be able to run the installed binaries

package `libc v0.2.154` in Cargo.lock is yanked in registry `crates-io`, consider running without --locked

default toolchain implicitly overridden with `nightly-2026-04-01-x86_64-unknown-linux-gnu` by environment variable

No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.