Skip to content

fix: bump yagr to 4.2.3 (#401) #342

fix: bump yagr to 4.2.3 (#401)

fix: bump yagr to 4.2.3 (#401) #342

Triggered via push January 30, 2024 15:36
Status Success
Total duration 2m 39s
Artifacts

release.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
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/
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
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3, codex-team/action-nodejs-package-info@v1, google-github-actions/release-please-action@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
release
The following actions uses node12 which is deprecated and will be forced to run on node16: codex-team/action-nodejs-package-info@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/