Skip to content
CI

fix: do not check for exactly one plugin in registry tests (#54) #131

Sign in to view logs

fix: do not check for exactly one plugin in registry tests (#54)

fix: do not check for exactly one plugin in registry tests (#54) #131

Triggered via push October 4, 2024 14:30
@johanneskoesterjohanneskoester
pushed 755e64e
main
Status Success
Total duration 2m 34s
Artifacts –

test.yml

on: push
formatting
18s
formatting
linting
2m 25s
linting
testing
23s
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/