Skip to content
CI

fix: do not check for exactly one plugin in registry tests #130

Sign in to view logs

fix: do not check for exactly one plugin in registry tests

fix: do not check for exactly one plugin in registry tests #130

Triggered via pull request October 4, 2024 14:22
@johanneskoesterjohanneskoester
opened #54
fix/test-check-plugin-count
Status Success
Total duration 2m 34s
Artifacts –

test.yml

on: pull_request
formatting
14s
formatting
linting
2m 25s
linting
testing
21s
testing
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
formatting
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
testing
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
linting
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/