chore(PST Regulation): extract in separate module #2158
bqth29Annotations
11 errors and 3 warnings
|
Build and test on ubuntu-latest with graalvm
Process completed with exit code 1.
|
|
Build and test on macos-latest with graalvm
The strategy configuration was canceled because "build.ubuntu-latest_graalvm" failed
|
|
Build and test on macos-latest with graalvm
Process completed with exit code 1.
|
|
Build and test on windows-latest with graalvm
The strategy configuration was canceled because "build.ubuntu-latest_graalvm" failed
|
|
Build and test on windows-latest with graalvm
The operation was canceled.
|
|
Build and test on windows-latest with java
The strategy configuration was canceled because "build.ubuntu-latest_graalvm" failed
|
|
Build and test on windows-latest with java
The operation was canceled.
|
|
Build and test on ubuntu-latest with java
The strategy configuration was canceled because "build.ubuntu-latest_graalvm" failed
|
|
Build and test on ubuntu-latest with java
The operation was canceled.
|
|
Build and test on macos-latest with java
The strategy configuration was canceled because "build.ubuntu-latest_graalvm" failed
|
|
Build and test on macos-latest with java
The operation was canceled.
|
|
Build and test on windows-latest with java
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@v1. 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 and test on ubuntu-latest with java
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@v1. 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 and test on macos-latest with java
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@v1. 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/
|