Skip to content

feat(compat): porting changes from version/1.21 to main. see #11647 … #1101

feat(compat): porting changes from version/1.21 to main. see #11647 …

feat(compat): porting changes from version/1.21 to main. see #11647 … #1101

Triggered via push June 8, 2026 07:38
Status Success
Total duration 5m 44s
Artifacts

release.yaml

on: push
release  /  Generate release information
5s
release / Generate release information
release  /  ...  /  compute-version
26s
release / compute-version / compute-version
release  /  🔴 Build notifications (start)
6s
release / 🔴 Build notifications (start)
release  /  gradle
4m 59s
release / gradle
release  /  🔴 Build notifications (end)
5s
release / 🔴 Build notifications (end)
Fit to window
Zoom out
Zoom in

Annotations

7 warnings and 3 notices
release / compute-version / compute-version
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, PaulHatch/semantic-version@v5.4.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
release / 🔴 Build notifications (start)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: neoforged/action-github-status@v1, neoforged/action-webhooks@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
release / gradle
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/create-release@v1, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-***-runners/
release / gradle
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-***-deprecating-save-state-and-set-output-commands/
release / gradle
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-***-deprecating-save-state-and-set-output-commands/
release / gradle
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-***-deprecating-save-state-and-set-output-commands/
release / 🔴 Build notifications (end)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: neoforged/action-github-status@v1, neoforged/action-webhooks@v1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
release / gradle
Submitted dependency-graph-reports/release-gradle.json: Dependency results for the repo have been successfully updated.
release / gradle
Submitted dependency-graph-reports/release-gradle-2.json: Dependency results for the repo have been successfully updated.
release / gradle
Submitted dependency-graph-reports/release-gradle-1.json: Dependency results for the repo have been successfully updated.