kengotoda / gradle-boilerplate Goto Github PK

🚨 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:

• Usage documentation
• Frequently Asked Questions
• Support channels

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 📦🚀

lint-staged is not working.

✔ Preparing...
⚠ Running tasks...
  ❯ Running tasks for *.{md,json,ts,tsx}
    ✖ prettier --write [ENOENT]
↓ Skipped because of errors from tasks. [SKIPPED]
✔ Reverting to original state because of errors...
✔ Cleaning up...

✖ prettier --write failed without output (ENOENT).
husky - pre-commit hook exited with code 1 (error)

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

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 resolve 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 is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

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
audited 776 packages in 4.296s

59 packages are looking for funding
run npm fund for details

found 0 vulnerabilities

Task :frontend:assembleFrontend UP-TO-DATE
Task :presentation:copyFrontendResources UP-TO-DATE
Task :presentation:processResources NO-SOURCE
Task :presentation:classes UP-TO-DATE
Task :presentation:jibDockerBuild FAILED
11 actionable tasks: 2 executed, 9 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 📦🚀

https://github.com/google/google-java-format/blob/master/README.md

#350 (comment)

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

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 resolve 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 master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

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.

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch master on the remote Git repository with URL https://x-access-token:[secure]@github.com/KengoTODA/gradle-boilerplate.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨

Your semantic-release bot 📦🚀