Skip to content

concord-server: fix session token handling (#1032) #2101

concord-server: fix session token handling (#1032)

concord-server: fix session token handling (#1032) #2101

Triggered via push November 8, 2024 18:56
Status Success
Total duration 1h 29m 18s
Artifacts

build.yml

on: push
check-labels
0s
check-labels
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
build (jdk17)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/setup-buildx-action@v2, actions/setup-java@v3, actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (jdk17-aarch64)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/setup-buildx-action@v2, actions/setup-java@v3, actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/