Skip to content

define and use pinned requirements (#60) #21

define and use pinned requirements (#60)

define and use pinned requirements (#60) #21

Triggered via push November 19, 2024 11:14
Status Success
Total duration 5m 7s
Artifacts 4

ci.yml

on: push
Matrix: build
Check flake8 rules
4s
Check flake8 rules
Check isort rules
6s
Check isort rules
Matrix: e2e
Publish (on release only)
0s
Publish (on release only)
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Check flake8 rules
The following actions use a deprecated Node.js version and will be forced to run on node20: 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/
Check isort rules
The following actions use a deprecated Node.js version and will be forced to run on node20: 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/

Artifacts

Produced during runtime
Name Size
action_image_artifact_convertit_latest
744 MB
debian-focal
7.87 MB
debian-jammy
6.79 MB
debian-noble
8.51 MB