Skip to content

[feat] add ci workflow to publish package to npm registry #21

[feat] add ci workflow to publish package to npm registry

[feat] add ci workflow to publish package to npm registry #21

Triggered via pull request January 16, 2024 22:30
Status Success
Total duration 6m 3s
Artifacts

internal-pr.yaml

on: pull_request
build_and_test  /  Build and Test
5m 52s
build_and_test / Build and Test
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build_and_test / Build and Test
The following actions uses node***2 which is deprecated and will be forced to run on node***6: pnpm/[email protected].***. For more info: https://github.blog/changelog/202***-06-***-github-actions-all-actions-will-run-on-node***6-instead-of-node***2-by-default/
build_and_test / Build and Test
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-***0-***-github-actions-deprecating-save-state-and-set-output-commands/
build_and_test / Build and Test
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-***0-***-github-actions-deprecating-save-state-and-set-output-commands/
build_and_test / Build and Test
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-***0-***-github-actions-deprecating-save-state-and-set-output-commands/