Skip to content

Avoid using ephemeral runners in publishing workflows since ephemeral runners are new feature and using them during the release can complicate the process. #1342

Avoid using ephemeral runners in publishing workflows since ephemeral runners are new feature and using them during the release can complicate the process.

Avoid using ephemeral runners in publishing workflows since ephemeral runners are new feature and using them during the release can complicate the process. #1342

Triggered via pull request February 10, 2025 21:43
Status Failure
Total duration 10m 52s
Artifacts

npm-cd.yml

on: pull_request
load-platform-matrix
4s
load-platform-matrix
start-self-hosted-runner
4m 8s
start-self-hosted-runner
Matrix: Publish packages to NPM
Publish the base NPM package
0s
Publish the base NPM package
Matrix: Test the release
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
ikolomi
approved Feb 10, 2025
AWS_ACTIONS

Annotations

5 errors and 1 warning
Publish packages to NPM (ubuntu, linux, arm64, aarch64-unknown-linux-musl, self-hosted, Linux, AR...
Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/ubuntu/actions-runner/_work/valkey-glide/valkey-glide/.github/workflows/setup-musl-on-linux'. Did you forget to run actions/checkout before running your local action?
Publish packages to NPM (macos, darwin, macos-14, arm64, aarch64-apple-darwin, pypi, npm, maven, ...
openssl@3 3.4.0 is already installed and up-to-date. To reinstall 3.4.0, run: brew reinstall openssl@3