-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The automated release is failing 🚨 #34
Comments
🚨 The automated release from the
|
added missing studip secret to workflow yaml fix #34
🎉 This issue has been resolved in version 1.1.0-beta.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 1.1.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🚨 The automated release from the
beta
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
beta
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.
Missing parameter url in plugin configuration
Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the
semantic-release-studip-webhook
plugin to add more helpful information.Good luck with your project ✨
Your semantic-release bot 📦🚀
The text was updated successfully, but these errors were encountered: