π¨ 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.
> Task :application:processResources NO-SOURCE
Task :infrastructure:processResources NO-SOURCE
Task :frontend:installNode SKIPPED
Task :frontend:installYarn SKIPPED
Task :domain:compileJava UP-TO-DATE
Task :infrastructure:compileJava UP-TO-DATE
Task :application:compileJava UP-TO-DATE
Task :application:classes UP-TO-DATE
Task :application:jar UP-TO-DATE
Task :domain:processResources NO-SOURCE
Task :domain:classes UP-TO-DATE
Task :domain:jar UP-TO-DATE
Task :infrastructure:classes UP-TO-DATE
Task :infrastructure:jar UP-TO-DATE
Task :presentation:compileJava UP-TO-DATE
Task :frontend:installFrontend FAILED
added 1 package, and audited 776 packages in 2s
1 moderate severity vulnerability
To address all issues, run:
npm audit fix
Run npm audit
for details.
8 actionable tasks: 1 executed, 7 up-to-date
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 π¦π