* What went wrong:
Some problems were found with the configuration of task ':publishPluginPublicationToHangar' (type 'HangarPublishTask').
  - Gradle detected a problem with the following location: '/home/runner/work/fastasyncvoxelsniper/fastasyncvoxelsniper/build/libs/fastasyncvoxelsniper-2.9.1.jar'.
    
    Reason: Task ':publishPluginPublicationToHangar' uses this output of task ':shadowJar' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
    
    Possible solutions:
      1. Declare task ':shadowJar' as an input of ':publishPluginPublicationToHangar'.
      2. Declare an explicit dependency on ':shadowJar' from ':publishPluginPublicationToHangar' using Task#dependsOn.
      3. Declare an explicit dependency on ':shadowJar' from ':publishPluginPublicationToHangar' using Task#mustRunAfter.
    
    Please refer to https://docs.gradle.org/8.1.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
  - Gradle detected a problem with the following location: '/home/runner/work/fastasyncvoxelsniper/fastasyncvoxelsniper/build/libs/fastasyncvoxelsniper-2.9.1.jar'.
    
    Reason: Task ':publishPluginPublicationToHangar' uses this output of task ':jar' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
    
    Possible solutions:
      1. Declare task ':jar' as an input of ':publishPluginPublicationToHangar'.
      2. Declare an explicit dependency on ':jar' from ':publishPluginPublicationToHangar' using Task#dependsOn.
      3. Declare an explicit dependency on ':jar' from ':publishPluginPublicationToHangar' using Task#mustRunAfter.
    
    Please refer to https://docs.gradle.org/8.1.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.