github-actions[bot]
commented
1 year ago :rotating_light: The automated release from the studio-v2 branch failed. :rotating_light:
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 studio-v2 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.5.0 on branch studio-v2 cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=1.4.14 <1.5.0 can be published from branch studio-v2.
The following commit is responsible for the invalid release:
- feat(search): add additional support for multi-faceted search (#106) (9cb9dc9)
This commit should be moved to a valid branch with git merge or git cherry-pick and removed from branch studio-v2 with git revert or git reset.
A valid branch could be main.
See the workflow configuration documentation for more details.
Good luck with your project ✨
Your semantic-release bot :package::rocket:
:rotating_light: The automated release from the
studio-v2branch failed. :rotating_light: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
studio-v2branch. 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.5.0on branchstudio-v2cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range
>=1.4.14 <1.5.0can be published from branchstudio-v2.The following commit is responsible for the invalid release:
This commit should be moved to a valid branch with git merge or git cherry-pick and removed from branch
studio-v2with git revert or git reset.A valid branch could be
main.See the workflow configuration documentation for more details.
Good luck with your project ✨
Your semantic-release bot :package::rocket: