Skip to content
build

Try to force a release from non-production branch #764

Sign in to view logs

Try to force a release from non-production branch

Try to force a release from non-production branch #764

Triggered via push September 22, 2023 10:43
@mart-rmart-r
pushed 2491b8a
v1.7.post
Status Success
Total duration 13m 23s
Artifacts –

main.yml

on: push
Matrix: build
publish-to-test-pypi
0s
publish-to-test-pypi
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build (3.9)
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/
build (3.10)
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/
build (3.8)
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/
build (3.11)
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/