Skip to content
Code Style

fix(ci): run wrapper verification after publishForge to avoid first-bump 404 #2099

Sign in to view logs

fix(ci): run wrapper verification after publishForge to avoid first-bump 404

fix(ci): run wrapper verification after publishForge to avoid first-bump 404 #2099

Triggered via pull request April 25, 2026 14:29
@jamesfredleyjamesfredley
synchronize #15602
fix/wrapper-verify-after-forge-publish
Status Success
Total duration 8m 52s
Artifacts 3

codestyle.yml

on: pull_request
Core Projects
8m 24s
Core Projects
Gradle Plugin Projects
1m 14s
Gradle Plugin Projects
Forge Projects
3m 38s
Forge Projects
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Gradle Plugin Projects
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@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/
Forge Projects
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@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/
Core Projects
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@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/

Artifacts

Produced during runtime
Name Size Digest
core-reports Expired
249 KB
sha256:f2fd95d6d64e25e78e6acfbd602a5ec3cf0bae5b773b52a0ff86d3c7cca255ff
forge-reports Expired
12.3 KB
sha256:dd99b8486de16e02874fd0061536e293af7a1f29588115452a1ad4c9b9ef222f
gradle-plugin-reports Expired
10.2 KB
sha256:69f2d1fcc5520cd86d9de0e17c5c31fab8e5481e4721543b19a78be3da9b9b35