Bump com.gradleup.shadow from 8.3.10 to 9.4.1

[dependabot]

Bumps com.gradleup.shadow from 8.3.10 to 9.4.1.

Release notes

Sourced from com.gradleup.shadow's releases.

9.4.1

Changed

• Update Kotlin to 2.3.20. (#1978)

9.4.0

Added

• Support Isolated Projects. (#1139)

Changed

• Allow opting out of adding shadowJar into assemble lifecycle. (#1939)

  shadow {
    // Disable making `assemble` task depend on `shadowJar`. This is enabled by default.
    addShadowJarToAssembleLifecycle = false
  }

• Stop catching ZipException when writing entries. (#1970)

Fixed

• Fix interaction with Gradle artifact transforms. (#1345)
• Fix skipStringConstants per-relocator behavior in mapName. (#1968)
• Fix failing for non-existent class directories. (#1976)

9.3.2

Changed

• Stop moving gradleApi dependency from api to compileOnly for Gradle 9.4+. (#1919)
• Log warnings for duplicates in the final JAR. (#1931)

Fixed

• Fix relocation patterns not included in task fingerprint. (#1933)

9.3.1

Fixed

• Use ASM from jdependency embedded. (#1898)
  This fixes potential classpath conflicts when using Shadow with other plugins that also use ASM.

9.3.0

Added

• Add PatternFilterableResourceTransformer to simplify pattern based ResourceTransformers. (#1849)
• Expose patternSet of ServiceFileTransformer as public. (#1849)
• Expose patternSet of ApacheLicenseResourceTransformer as public. (#1850)
• Expose patternSet of ApacheNoticeResourceTransformer as public. (#1850)

... (truncated)

Commits

• f98d8f2 Prepare version 9.4.1
• 7cf1ac5 Note #1978 in changelog
• 539d532 Update plugin jetbrains-dokka to v2.2.0 (#1994)
• 0fb99ca Update actions/deploy-pages action to v5 (#1993)
• 38ec3e2 Update Develocity to v4.4.0 (#1992)
• e519072 Update gradle/actions action to v6 (#1990)
• ca0dd71 Update pluginPublish to v2.1.1 (#1989)
• 5a1ab58 Update Gradle to v9.4.1 (#1988)
• 69dfdfc Improve file type check for AAR (#1987)
• 1395087 Document excluding non-JAR transitive dependencies (#1986)
• Additional commits viewable in compare view

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

A newer version of com.gradleup.shadow exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

[wmdietl]

@copilot Why is CI failing?

[Copilot]

@copilot Why is CI failing?

The CI failures are not related to this PR's changes. Every failing job shows the same transient infrastructure error during Java setup:

Java setup process failed due to: error code: 520

HTTP 520 is a Cloudflare "Unknown Error" — it means the JDK download endpoint was temporarily unreachable when the jobs ran. Re-running the failed CI jobs should resolve this.

[wmdietl]

@copilot Look at the CI failures again. I see

* What went wrong:
Execution failed for task ':checker:shadowJar'.
> neither file nor directory

[Copilot]

@copilot Look at the CI failures again. I see

...

The failure is caused by a breaking change in Shadow 9.x: it now adds a shadowRuntimeElements variant (with Usage=java-runtime, LibraryElements=jar) to each subproject's java component. When checker:shadowJar runs with minimize(), it resolves checker's runtimeClasspath to build UnusedTracker. Gradle then selects the shadowRuntimeElements variant for dependency projects (e.g. framework) instead of runtimeElements, returning the shadow JAR path (framework-X-all.jar). Since framework:shadowJar hasn't run, that file doesn't exist — UnusedTracker.addClazzpathUnit() throws "neither file nor directory".

Fixed in commit 1e36b04 by adding shadow { addShadowVariantIntoJavaComponent = false } to the allprojects {} block in root build.gradle. This restores the Shadow 8.x behavior where only the regular runtimeElements variant is published, preventing the wrong variant from being selected during dependency resolution.

[wmdietl]

@copilot It doesn't look like your change achieved anything. CI is still failing with the same error. Can you try again?

[Copilot]

@copilot It doesn't look like your change achieved anything. CI is still failing with the same error. Can you try again?

The previous fix was wrong — addShadowVariantIntoJavaComponent = false only removes the variant from Maven publication; it does not prevent Gradle from selecting shadowRuntimeElements during local inter-project dependency resolution.

Root cause: Shadow 9.x registers a shadowRuntimeElements configuration (with Usage=java-runtime, LibraryElements=jar) as a consumable variant on every subproject. When checker:shadowJar runs its minimize() step, it resolves checker:runtimeClasspath to build the UnusedTracker. For project dependencies (e.g. framework), Gradle's variant selection may choose shadowRuntimeElements instead of runtimeElements, returning the shadow JAR path (framework-X-all.jar). Since framework:shadowJar hasn't run, that file doesn't exist, and UnusedTracker.addClazzpathUnit() throws "neither file nor directory".

Fix (commit 2709451): In the subprojects {} block, use configurations.configureEach to mark shadowRuntimeElements as canBeConsumed = false on every subproject. This prevents Gradle from selecting the shadow variant during inter-project resolution, ensuring runtimeElements (the regular framework.jar) is always used.