Skip to content

fix: Use Spring's native CSRF protection, and fix login page #20317

fix: Use Spring's native CSRF protection, and fix login page

fix: Use Spring's native CSRF protection, and fix login page #20317

Triggered via pull request November 9, 2024 01:49
Status Success
Total duration 26m 36s
Artifacts 3

quality-checks.yml

on: pull_request
path-filter
11s
path-filter
server-spotless  /  spotless-check
2m 8s
server-spotless / spotless-check
server-unit-tests  /  server-unit-tests
25m 59s
server-unit-tests / server-unit-tests
client-build  /  client-build
10m 20s
client-build / client-build
client-prettier  /  prettier-check
2m 26s
client-prettier / prettier-check
client-unit-tests  /  client-unit-tests
7m 49s
client-unit-tests / client-unit-tests
client-lint  /  client-lint
5m 12s
client-lint / client-lint
client-check-cyclic-deps  /  check-cyclic-dependencies
1m 10s
client-check-cyclic-deps / check-cyclic-dependencies
qc-result
0s
qc-result
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
path-filter
The following actions use a deprecated Node.js version and will be forced to run on node20: dorny/paths-filter@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
client-prettier / prettier-check
Cache save failed.
client-lint / client-lint
Cache save failed.

Artifacts

Produced during runtime
Name Size
client-build
88.5 MB
failed-server-tests
162 Bytes
server-build
571 MB