Skip to content

Temporary issues on the production instance #179

Temporary issues on the production instance

Temporary issues on the production instance #179

Triggered via issue October 18, 2023 06:25
Status Success
Total duration 20s
Artifacts

labeled_issue.yml

on: issues
Move "under development" issues
10s
Move "under development" issues
Move "ready for testings" issues
6s
Move "ready for testings" issues
Move "solved" issues
5s
Move "solved" issues
Move "deployed in reference validator" issues
7s
Move "deployed in reference validator" issues
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Move "solved" issues
The following actions uses node12 which is deprecated and will be forced to run on node16: konradpabjan/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Move "ready for testings" issues
The following actions uses node12 which is deprecated and will be forced to run on node16: konradpabjan/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Move "deployed in reference validator" issues
The following actions uses node12 which is deprecated and will be forced to run on node16: konradpabjan/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Move "under development" issues
The following actions uses node12 which is deprecated and will be forced to run on node16: konradpabjan/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/