Skip to content

Unclear way on how to use custom resolver structure #607

Unclear way on how to use custom resolver structure

Unclear way on how to use custom resolver structure #607

Triggered via issue August 19, 2024 17:02
@jorgev259jorgev259
commented on #328 029d791
Status Success
Total duration 17s
Artifacts

snapshot.yml

on: issue_comment
release-check
5s
release-check
release
0s
release
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
release-check
The following actions uses node12 which is deprecated and will be forced to run on node16: khan/pull-request-comment-trigger@v1.1.0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
release-check
The following actions use a deprecated Node.js version and will be forced to run on node20: khan/pull-request-comment-trigger@v1.1.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
release-check
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-check
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/