Skip to content

[#22] - implement per-realm JWT secret rotation with lifecycle management #16

[#22] - implement per-realm JWT secret rotation with lifecycle management

[#22] - implement per-realm JWT secret rotation with lifecycle management #16

Triggered via pull request April 24, 2026 16:46
Status Success
Total duration 1m 41s
Artifacts
changes
5s
changes
quality-assurance-backend  /  quality-assurance
1m 29s
quality-assurance-backend / quality-assurance
quality-assurance-sdk  /  quality-assurance
54s
quality-assurance-sdk / quality-assurance
quality-assurance-contracts  /  quality-assurance
quality-assurance-contracts / quality-assurance
quality-assurance-proxy  /  quality-assurance
quality-assurance-proxy / quality-assurance
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
quality-assurance-sdk / quality-assurance
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
quality-assurance-backend / quality-assurance
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/