The automated release is failing 🚨
brent-spiner opened this issue · 3 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.
HTTPError: Response code 400 (Bad Request)
Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the semantic-release-chrome plugin to add more helpful information.
Good luck with your project ✨
Your semantic-release bot 📦🚀
Publishing to Chrome Webstore has been successful, but has failed to Edge Webstore.
Edge Webstore is complaining as follows:
Package acceptance validation error: The translation for field Description in locale pt_BR is too long: 'Faça um Shift Left na sua segurança instalando a extensão da Plataforma Sonatype - Escaneie repositórios de código aberto em busca de vulnerabilidades conhecidas.'. It exceeds maximum size limit of 132 characters.