The automated release is failing 🚨
opened this issue · comments
🚨 The automated release from the 1.150.x 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 1.150.x 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.
The release 1.150.6 on branch 1.150.x cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=1.150.5 <1.137.0 can be published from branch 1.150.x.
The following commit is responsible for the invalid release:
- fix: DE44538: add an await updatecomplete for content to render before getting content container (#1523) (#1531) (c0c0f06)
This commit should be moved to a valid branch with git merge or git cherry-pick and removed from branch 1.150.x with git revert or git reset.
A valid branch could be 1.100.x, 1.111.x, 1.118.x, 1.131.x, 1.78.x, 1.85.x or master.
See the workflow configuration documentation for more details.
Good luck with your project ✨
Your semantic-release bot 📦🚀