Skip to content

chore(PST Regulation): extract in separate module #3925

chore(PST Regulation): extract in separate module

chore(PST Regulation): extract in separate module #3925

Triggered via pull request March 20, 2026 15:24
Status Success
Total duration 36s
Artifacts

build_doc.yml

on: pull_request
⚙️ Build documentation on Ubuntu
31s
⚙️ Build documentation on Ubuntu
🔗 Look for broken links
29s
🔗 Look for broken links
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
🔗 Look for broken links
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
⚙️ Build documentation on Ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/