search

LabShare-Archive / services-cache

Cache plugin for LabShare Services
MIT License
1 stars 6 forks source link

The automated release is failing 🚨 #101

Closed JamilOmar closed 4 years ago

JamilOmar commented 4 years ago

:rotating_light: The automated release from the 1x branch failed. :rotating_light:

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 1x 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 1.0.1 on branch 1x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=2.0.2 can be published from branch 1x.

The following commits are responsible for the invalid release:

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 1x with git revert or git reset.

A valid branch could be master or 1x.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot :package::rocket:

JamilOmar commented 4 years ago

:rotating_light: The automated release from the 1x branch failed. :rotating_light:

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 1x 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 1.18.509 on branch 1x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=2.0.2 can be published from branch 1x.

The following commits are responsible for the invalid release:

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 1x with git revert or git reset.

A valid branch could be master or 1x.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot :package::rocket:

JamilOmar commented 4 years ago

:rotating_light: The automated release from the 1x branch failed. :rotating_light:

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 1x 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 1.18.509 on branch 1x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=2.0.2 can be published from branch 1x.

The following commits are responsible for the invalid release:

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 1x with git revert or git reset.

A valid branch could be master or 1x.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot :package::rocket: