The automated release is failing 🚨
github-actions opened this issue · 11 comments
🚨 The automated release from the main branch failed. 🚨
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
Welcome to Gradle 7.2!
Here are the highlights of this release:
- Toolchain support for Scala
- More cache hits when Java source files have platform-specific line endings
- More resilient remote HTTP build cache behavior
For more details see https://docs.gradle.org/7.2/release-notes.html
Starting a Gradle Daemon (subsequent builds will be faster)
Configure project :
Fabric Loom: 0.9.54
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merging /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny with /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merged mappings written to /home/runner/.gradle/caches/fabric-loom/mappings/steps/unordered-merged.tiny
:remapping minecraft (TinyRemapper, official -> named)
:remapping minecraft (TinyRemapper, official -> intermediary)
:remapping 48 mods (TinyRemapper, intermediary -> named)
Task :clean
Task :compileJava
Task :processResources
Task :classes
Task :checkstyleMain
Task :checkstyleMain FAILED
4 actionable tasks: 4 executed
Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the @semantic-release/exec plugin to add more helpful information.
Good luck with your project ✨
Your semantic-release bot 📦🚀
🚨 The automated release from the main branch failed. 🚨
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
Welcome to Gradle 7.2!
Here are the highlights of this release:
- Toolchain support for Scala
- More cache hits when Java source files have platform-specific line endings
- More resilient remote HTTP build cache behavior
For more details see https://docs.gradle.org/7.2/release-notes.html
Starting a Gradle Daemon (subsequent builds will be faster)
Configure project :
Fabric Loom: 0.9.54
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merging /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny with /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merged mappings written to /home/runner/.gradle/caches/fabric-loom/mappings/steps/unordered-merged.tiny
:remapping minecraft (TinyRemapper, official -> named)
:remapping minecraft (TinyRemapper, official -> intermediary)
:remapping 48 mods (TinyRemapper, intermediary -> named)
Task :clean
Task :compileJava
Task :processResources
Task :classes
Task :checkstyleMain
Task :checkstyleMain FAILED
4 actionable tasks: 4 executed
Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the @semantic-release/exec plugin to add more helpful information.
Good luck with your project ✨
Your semantic-release bot 📦🚀
🚨 The automated release from the main branch failed. 🚨
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
Welcome to Gradle 7.2!
Here are the highlights of this release:
- Toolchain support for Scala
- More cache hits when Java source files have platform-specific line endings
- More resilient remote HTTP build cache behavior
For more details see https://docs.gradle.org/7.2/release-notes.html
Starting a Gradle Daemon (subsequent builds will be faster)
Configure project :
Fabric Loom: 0.9.54
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merging /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny with /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merged mappings written to /home/runner/.gradle/caches/fabric-loom/mappings/steps/unordered-merged.tiny
:remapping minecraft (TinyRemapper, official -> named)
:remapping minecraft (TinyRemapper, official -> intermediary)
:remapping 48 mods (TinyRemapper, intermediary -> named)
Task :clean
Task :compileJava
Task :processResources
Task :classes
Task :checkstyleMain
Task :checkstyleMain FAILED
4 actionable tasks: 4 executed
Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the @semantic-release/exec plugin to add more helpful information.
Good luck with your project ✨
Your semantic-release bot 📦🚀
🚨 The automated release from the main branch failed. 🚨
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
Welcome to Gradle 7.2!
Here are the highlights of this release:
- Toolchain support for Scala
- More cache hits when Java source files have platform-specific line endings
- More resilient remote HTTP build cache behavior
For more details see https://docs.gradle.org/7.2/release-notes.html
Starting a Gradle Daemon (subsequent builds will be faster)
Configure project :
Fabric Loom: 0.9.54
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merging /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny with /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merged mappings written to /home/runner/.gradle/caches/fabric-loom/mappings/steps/unordered-merged.tiny
:remapping minecraft (TinyRemapper, official -> named)
:remapping minecraft (TinyRemapper, official -> intermediary)
:remapping 48 mods (TinyRemapper, intermediary -> named)
Task :clean
Task :compileJava
Task :processResources
Task :classes
Task :checkstyleMain
Task :checkstyleMain FAILED
4 actionable tasks: 4 executed
Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the @semantic-release/exec plugin to add more helpful information.
Good luck with your project ✨
Your semantic-release bot 📦🚀
🚨 The automated release from the main branch failed. 🚨
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
Welcome to Gradle 7.2!
Here are the highlights of this release:
- Toolchain support for Scala
- More cache hits when Java source files have platform-specific line endings
- More resilient remote HTTP build cache behavior
For more details see https://docs.gradle.org/7.2/release-notes.html
Starting a Gradle Daemon (subsequent builds will be faster)
Configure project :
Fabric Loom: 0.9.54
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merging /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny with /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merged mappings written to /home/runner/.gradle/caches/fabric-loom/mappings/steps/unordered-merged.tiny
:remapping minecraft (TinyRemapper, official -> named)
:remapping minecraft (TinyRemapper, official -> intermediary)
:remapping 48 mods (TinyRemapper, intermediary -> named)
Task :clean
Task :compileJava
Task :processResources
Task :classes
Task :checkstyleMain
Task :checkstyleMain FAILED
4 actionable tasks: 4 executed
Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the @semantic-release/exec plugin to add more helpful information.
Good luck with your project ✨
Your semantic-release bot 📦🚀
🚨 The automated release from the main branch failed. 🚨
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
Welcome to Gradle 7.2!
Here are the highlights of this release:
- Toolchain support for Scala
- More cache hits when Java source files have platform-specific line endings
- More resilient remote HTTP build cache behavior
For more details see https://docs.gradle.org/7.2/release-notes.html
Starting a Gradle Daemon (subsequent builds will be faster)
Configure project :
Fabric Loom: 0.9.54
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merging /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny with /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merged mappings written to /home/runner/.gradle/caches/fabric-loom/mappings/steps/unordered-merged.tiny
:remapping minecraft (TinyRemapper, official -> named)
:remapping minecraft (TinyRemapper, official -> intermediary)
:remapping 48 mods (TinyRemapper, intermediary -> named)
Task :clean
Task :compileJava
Task :processResources
Task :classes
Task :checkstyleMain
Task :checkstyleMain FAILED
4 actionable tasks: 4 executed
Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the @semantic-release/exec plugin to add more helpful information.
Good luck with your project ✨
Your semantic-release bot 📦🚀
🚨 The automated release from the main branch failed. 🚨
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
Welcome to Gradle 7.2!
Here are the highlights of this release:
- Toolchain support for Scala
- More cache hits when Java source files have platform-specific line endings
- More resilient remote HTTP build cache behavior
For more details see https://docs.gradle.org/7.2/release-notes.html
Starting a Gradle Daemon (subsequent builds will be faster)
Configure project :
Fabric Loom: 0.9.54
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merging /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny with /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merged mappings written to /home/runner/.gradle/caches/fabric-loom/mappings/steps/unordered-merged.tiny
:remapping minecraft (TinyRemapper, official -> named)
:remapping minecraft (TinyRemapper, official -> intermediary)
:remapping 49 mods (TinyRemapper, intermediary -> named)
Task :clean
Task :compileJava
Task :processResources
Task :classes
Task :checkstyleMain
Task :checkstyleMain FAILED
4 actionable tasks: 4 executed
Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the @semantic-release/exec plugin to add more helpful information.
Good luck with your project ✨
Your semantic-release bot 📦🚀
🚨 The automated release from the main branch failed. 🚨
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
Welcome to Gradle 7.2!
Here are the highlights of this release:
- Toolchain support for Scala
- More cache hits when Java source files have platform-specific line endings
- More resilient remote HTTP build cache behavior
For more details see https://docs.gradle.org/7.2/release-notes.html
Starting a Gradle Daemon (subsequent builds will be faster)
Configure project :
Fabric Loom: 0.9.54
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merging /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny with /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merged mappings written to /home/runner/.gradle/caches/fabric-loom/mappings/steps/unordered-merged.tiny
:remapping minecraft (TinyRemapper, official -> named)
:remapping minecraft (TinyRemapper, official -> intermediary)
:remapping 49 mods (TinyRemapper, intermediary -> named)
Task :clean
Task :compileJava
Task :processResources
Task :classes
Task :checkstyleMain
Task :checkstyleMain FAILED
4 actionable tasks: 4 executed
Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the @semantic-release/exec plugin to add more helpful information.
Good luck with your project ✨
Your semantic-release bot 📦🚀
🚨 The automated release from the main branch failed. 🚨
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
Welcome to Gradle 7.2!
Here are the highlights of this release:
- Toolchain support for Scala
- More cache hits when Java source files have platform-specific line endings
- More resilient remote HTTP build cache behavior
For more details see https://docs.gradle.org/7.2/release-notes.html
Starting a Gradle Daemon (subsequent builds will be faster)
Configure project :
Fabric Loom: 0.9.54
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merging /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny with /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merged mappings written to /home/runner/.gradle/caches/fabric-loom/mappings/steps/unordered-merged.tiny
:remapping minecraft (TinyRemapper, official -> named)
:remapping minecraft (TinyRemapper, official -> intermediary)
:remapping 49 mods (TinyRemapper, intermediary -> named)
Task :clean
Task :compileJava
Task :processResources
Task :classes
Task :checkstyleMain
Task :checkstyleMain FAILED
4 actionable tasks: 4 executed
Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the @semantic-release/exec plugin to add more helpful information.
Good luck with your project ✨
Your semantic-release bot 📦🚀
🚨 The automated release from the main branch failed. 🚨
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
Welcome to Gradle 7.2!
Here are the highlights of this release:
- Toolchain support for Scala
- More cache hits when Java source files have platform-specific line endings
- More resilient remote HTTP build cache behavior
For more details see https://docs.gradle.org/7.2/release-notes.html
Starting a Gradle Daemon (subsequent builds will be faster)
Configure project :
Fabric Loom: 0.9.54
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merging /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny with /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merged mappings written to /home/runner/.gradle/caches/fabric-loom/mappings/steps/unordered-merged.tiny
:remapping minecraft (TinyRemapper, official -> named)
:remapping minecraft (TinyRemapper, official -> intermediary)
:remapping 49 mods (TinyRemapper, intermediary -> named)
Task :clean
Task :compileJava
Task :processResources
Task :classes
Task :checkstyleMain
Task :checkstyleMain FAILED
4 actionable tasks: 4 executed
Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the @semantic-release/exec plugin to add more helpful information.
Good luck with your project ✨
Your semantic-release bot 📦🚀
🚨 The automated release from the main branch failed. 🚨
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
Welcome to Gradle 7.2!
Here are the highlights of this release:
- Toolchain support for Scala
- More cache hits when Java source files have platform-specific line endings
- More resilient remote HTTP build cache behavior
For more details see https://docs.gradle.org/7.2/release-notes.html
Starting a Gradle Daemon (subsequent builds will be faster)
Configure project :
Fabric Loom: 0.9.54
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merging /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny with /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merged mappings written to /home/runner/.gradle/caches/fabric-loom/mappings/steps/unordered-merged.tiny
:remapping minecraft (TinyRemapper, official -> named)
:remapping minecraft (TinyRemapper, official -> intermediary)
:remapping 52 mods (TinyRemapper, intermediary -> named)
Task :clean
Task :compileJava
Task :compileJava FAILED
2 actionable tasks: 2 executed
Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the @semantic-release/exec plugin to add more helpful information.
Good luck with your project ✨
Your semantic-release bot 📦🚀
🚨 The automated release from the main branch failed. 🚨
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
Welcome to Gradle 7.2!
Here are the highlights of this release:
- Toolchain support for Scala
- More cache hits when Java source files have platform-specific line endings
- More resilient remote HTTP build cache behavior
For more details see https://docs.gradle.org/7.2/release-notes.html
Starting a Gradle Daemon (subsequent builds will be faster)
Configure project :
Fabric Loom: 0.9.54
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny
Reading /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merging /home/runner/.gradle/caches/fabric-loom/mappings/steps/inverted-intermediary.tiny with /home/runner/.gradle/caches/fabric-loom/mappings/steps/unmerged-yarn.tiny
Merged mappings written to /home/runner/.gradle/caches/fabric-loom/mappings/steps/unordered-merged.tiny
:remapping minecraft (TinyRemapper, official -> named)
:remapping minecraft (TinyRemapper, official -> intermediary)
:remapping 52 mods (TinyRemapper, intermediary -> named)
Task :clean
Task :compileJava
Task :compileJava FAILED
2 actionable tasks: 2 executed
Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the @semantic-release/exec plugin to add more helpful information.
Good luck with your project ✨
Your semantic-release bot 📦🚀