Fix interfaces being injected after permits clause (#64) #57
Matyrobbrtrelease.yml
on: push
release
/
Compute version
5s
release
/
Build notifications (start)
5s
release
/
gradle
5m 8s
release
/
Build notifications (end)
5s
Annotations
14 warnings
|
release / Compute version
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: neoforged/action-tag-versioning@v2. 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/
|
|
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 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/
|
|
release / gradle
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: gradle/actions/setup-gradle@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/
|
|
release / gradle:
api/src/main/java/net/neoforged/jst/api/FileEntry.java#L20
no main description
|
|
|
|
release / gradle:
api/src/main/java/net/neoforged/jst/api/FileEntry.java#L10
no main description
|
|
|
|
|
|
release / gradle:
api/src/main/java/net/neoforged/jst/api/FileEntries.java#L29
no @param for zipEntry
|
|
release / gradle:
api/src/main/java/net/neoforged/jst/api/FileEntries.java#L29
no @param for zipFile
|
|
|
|
|
|
release / gradle:
api/src/main/java/net/neoforged/jst/api/FileEntries.java#L16
no @param for sourceRoot
|
|
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 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/
|