Skip to content

update configuration to YAML #983

update configuration to YAML

update configuration to YAML #983

Triggered via pull request January 6, 2024 13:27
@kalxaskalxas
synchronize #937
yaml-config
Status Success
Total duration 1m 59s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

main.yml

on: pull_request
Matrix: main
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
main (3.11, py311-sqlite)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
main (3.8, py38-sqlite)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
main (3.9, py39-sqlite)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
main (3.10, py310-sqlite)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/