Skip to content
Build

Bump flask-talisman from 1.0.0 to 1.1.0 #659

Sign in to view logs

Bump flask-talisman from 1.0.0 to 1.1.0

Bump flask-talisman from 1.0.0 to 1.1.0 #659

Triggered via push August 3, 2023 21:52
@dependabotdependabot[bot]
pushed 1916a32
dependabot/pip/flask-talisman-1.1.0
Status Failure
Total duration 41s
Artifacts –

pythonpackage.yml

on: push
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 4 warnings
build (3.8)
Process completed with exit code 2.
build (3.10)
Process completed with exit code 2.
build (3.11)
The operation was canceled.
build (3.9)
The operation was canceled.
build (3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/