Skip to content

fix: release npm sequentially after github #4

fix: release npm sequentially after github

fix: release npm sequentially after github #4

Triggered via push January 24, 2024 12:52
Status Failure
Total duration 2m 47s
Artifacts 1

release.yml

on: push
Release on Github
11s
Release on Github
Release on NPM registry
18s
Release on NPM registry
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
Release on NPM registry
Process completed with exit code 1.
Release on Github
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2, konfer-be/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Release on Github
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Release on NPM registry
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Artifacts

Produced during runtime
Name Size
build-files Expired
159 KB