Skip to content

approve-command

approve-command #64

Triggered via repository dispatch October 22, 2024 05:58
@BSData-botBSData-bot
approve-command 1d92c26
Status Success
Total duration 45s
Artifacts

approve-command.yml

on: repository_dispatch
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
approve
The following actions uses node12 which is deprecated and will be forced to run on node16: peter-evans/create-or-update-comment@v1, actions/github-script@v1, actions/checkout@v2, actions/github-script@v3, peter-evans/close-issue@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
approve
The following actions use a deprecated Node.js version and will be forced to run on node20: peter-evans/create-or-update-comment@v1, actions/github-script@v1, actions/checkout@v2, actions/github-script@v3, peter-evans/close-issue@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
approve
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/
approve
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/