Skip to content

Expose a way to force unpublished event to be published #565

Expose a way to force unpublished event to be published

Expose a way to force unpublished event to be published #565

Triggered via push August 2, 2024 07:13
Status Failure
Total duration 8m 2s
Artifacts

test.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

1 error and 5 warnings
test
Process completed with exit code 127.
test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2.2.0, actions/setup-java@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2.2.0, actions/setup-java@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
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-10-11-github-actions-deprecating-save-state-and-set-output-commands/
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-10-11-github-actions-deprecating-save-state-and-set-output-commands/
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-10-11-github-actions-deprecating-save-state-and-set-output-commands/