Skip to content

fix inability to reference same-named Kinds #11

fix inability to reference same-named Kinds

fix inability to reference same-named Kinds #11

Triggered via pull request September 3, 2024 17:38
Status Success
Total duration 4m 38s
Artifacts

test.yml

on: pull_request
Matrix: test-all
Matrix: test-skip-kind
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
test-all (1.19, ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: helm/kind-action@dda0770415bac9fc20092cacbc54aa298604d140. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-all (1.20, ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: helm/kind-action@dda0770415bac9fc20092cacbc54aa298604d140. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-all (1.21, ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: helm/kind-action@dda0770415bac9fc20092cacbc54aa298604d140. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/