Skip to content
ci

ci: Use GITHUB_OUTPUT envvar instead of set-output command #572

Sign in to view logs

ci: Use GITHUB_OUTPUT envvar instead of set-output command

ci: Use GITHUB_OUTPUT envvar instead of set-output command #572

Re-run triggered January 20, 2024 15:37
@kingdonbkingdonb
#502
main
Status Success
Total duration 2m 10s
Artifacts –

ci.yml

on: pull_request
e2e-testing
2m 1s
e2e-testing
Fit to window
Zoom out
Zoom in

Annotations

1 warning
e2e-testing
The following actions uses node12 which is deprecated and will be forced to run on node16: engineerd/setup-kind@aa272fe2a7309878ffc2a81c56cfe3ef108ae7d0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/