Skip to content

Publish npm packages #239

Publish npm packages

Publish npm packages #239

Manually triggered August 16, 2023 14:15
Status Success
Total duration 29m 9s
Artifacts

npm-publish.yml

on: workflow_dispatch
both  /  ...  /  publish_main
14m 26s
both / both_main / publish_main
both  /  ...  /  publish_rc
0s
both / both_main / publish_rc
both  /  ...  /  publish_hotfix
0s
both / both_main / publish_hotfix
hotfix  /  publish_hotfix
hotfix / publish_hotfix
hotfix  /  publish_main
hotfix / publish_main
hotfix  /  publish_rc
hotfix / publish_rc
main  /  publish_hotfix
main / publish_hotfix
main  /  publish_main
main / publish_main
main  /  publish_rc
main / publish_rc
rc  /  publish_hotfix
rc / publish_hotfix
rc  /  publish_main
rc / publish_main
rc  /  publish_rc
rc / publish_rc
rc-followup  /  publish_hotfix
rc-followup / publish_hotfix
rc-followup  /  publish_main
rc-followup / publish_main
rc-followup  /  publish_rc
rc-followup / publish_rc
both  /  ...  /  publish_main
0s
both / both_rc / publish_main
both  /  ...  /  publish_rc
14m 19s
both / both_rc / publish_rc
both  /  ...  /  publish_hotfix
0s
both / both_rc / publish_hotfix
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
both / both_main / publish_main
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
both / both_rc / publish_rc
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/