The automated release is failing 🚨 #1199
Description
🚨 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:
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 2.24.0 on branch master cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=2.23.1 <2.24.0-next.1 can be published from branch master.
The following commits are responsible for the invalid release:
- feat: add placeholderData to queryObserver (feat: add placeholderData to queryObserver #1161) (3fce2ec)
- docs(typescript): add note for custom hooks types (docs(typescript): add note for custom hooks types #1185) (6e30aaa)
- docs(api): change manual to isEnabled (docs(api): change manual to isEnabled #1166) (160d1ac)
- docs: update sponsors (5bfd7af)
- docs: update sponsors (7f35693)
- docs(examples): fix sandbox version (df4c755)
- docs(examples): fix sandbox version (8001abb)
- docs(examples): fix sandbox version (3073ddd)
- docs(examples): fix sandbox version (40944e1)
- docs(examples): fix sandbox version (a7cff10)
- docs(examples): fix sandbox version (21803e3)
- docs(examples): fix sandbox version (39c021c)
- docs(examples): fix sandbox version (7352b8b)
- docs(examples): fix codesandbox version (35060bd)
- fully automate the dev setup with Gitpod. (Easier Contributions. #1155) (812f1e9)
- docs: Remove unnecessary --save in install instructions (Remove unnecessary --save in install instructions #1149) (07f06b9)
- docs: GQL Blog Example (GQL Blog Example #1144) (8582a9a)
- docs(nextjs-example) init (Add nextjs example #1146) (8585a17)
- Fix Typo (docs(guides): Fix a typo #1145) (0d97ece)
- build: add beta builds (833f518)
- docs: Elaborate on usage of queries (docs: Elaborate on usage of queries #1133) (8669fad)
- docs: Add eslint-config-prettier to devDependencies in custom-hooks example (Add eslint-config-prettier to devDependencies in custom-hooks example #1127) (6756050)
- build: add building support on Windows terminal (build: add building support on Windows terminal #1129) (4a7ca0c)
Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch master with git revert or git reset.
A valid branch could be 1.x, master or beta.
See the workflow configuration documentation for more details.
Good luck with your project ✨
Your semantic-release bot 📦🚀