Skip to content
Build

use new RELEASE statusChangeCommand type instead of hardcoded FREE status, when releasing objects #504

Sign in to view logs

use new RELEASE statusChangeCommand type instead of hardcoded FREE status, when releasing objects

use new RELEASE statusChangeCommand type instead of hardcoded FREE status, when releasing objects #504

Triggered via pull request September 27, 2024 11:22
@bverbekenbverbeken
synchronize #199
use-new-RELEASE-statusChangeCommand-type-instead-of-hardcoded-FREE-status
Status Success
Total duration 2m 3s
Artifacts –

build.yml

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

Annotations

2 warnings
build (21)
The following actions use a deprecated Node.js version and will be forced to run on node20: zcong1993/setup-timezone@master. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (11)
The following actions use a deprecated Node.js version and will be forced to run on node20: zcong1993/setup-timezone@master. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/