Skip to content

ci: Use GITHUB_OUTPUT envvar instead of set-output command (#20) #20

ci: Use GITHUB_OUTPUT envvar instead of set-output command (#20)

ci: Use GITHUB_OUTPUT envvar instead of set-output command (#20) #20

Triggered via push January 19, 2024 16:40
Status Failure
Total duration 19s
Artifacts

release.yml

on: push
Release
8s
Release
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
Release
Process completed with exit code 1.
Release
The following actions uses node12 which is deprecated and will be forced to run on node16: pnpm/[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
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-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Release
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
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/