Skip to content
CI

fix: the release env should upgrade JDK 17 as well #68

Sign in to view logs

fix: the release env should upgrade JDK 17 as well

fix: the release env should upgrade JDK 17 as well #68

Triggered via pull request December 25, 2023 08:22
@2BAB2BAB
opened #13
dev
Status Success
Total duration 9m 2s
Artifacts –

ci.yml

on: pull_request
Assemble
3m 28s
Assemble
Checks (unit tests and static analysis, TODO:add detekt check after set it up)
3m 47s
Checks (unit tests and static analysis, TODO:add detekt check after set it up)
Functional Tests
8m 53s
Functional Tests
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Assemble
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Checks (unit tests and static analysis, TODO:add detekt check after set it up)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Functional Tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/