search

rubencabrera / odoo-base-images

Base docker images for odoo-docker with OCA repos.
Apache License 2.0
0 stars 1 forks source link

The automated release is failing 🚨 #50

Closed github-actions[bot] closed 1 year ago

github-actions[bot] commented 1 year ago

:rotating_light: The automated release from the 12.x 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 12.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.0.0 on branch 12.x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=12.0.0 <1.0.0 can be published from branch 12.x.

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 12.x with git revert or git reset.

A valid branch could be master.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot :package::rocket:

github-actions[bot] commented 1 year ago

:rotating_light: The automated release from the 12.x 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 12.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.0.0 on branch 12.x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=12.0.0 <1.0.0 can be published from branch 12.x.

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 12.x with git revert or git reset.

A valid branch could be master.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot :package::rocket:

github-actions[bot] commented 1 year ago

:rotating_light: The automated release from the 12.x 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 12.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.0.0 on branch 12.x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=12.0.0 <1.0.0 can be published from branch 12.x.

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 12.x with git revert or git reset.

A valid branch could be master.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot :package::rocket:

github-actions[bot] commented 1 year ago

:rotating_light: The automated release from the 12.x 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 12.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.0.0 on branch 12.x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=12.0.0 <1.0.0 can be published from branch 12.x.

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 12.x with git revert or git reset.

A valid branch could be master.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot :package::rocket:

github-actions[bot] commented 1 year ago

:rotating_light: The automated release from the 12.x 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 12.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 14.0.2 on branch 12.x cannot be published as it is out of range.

Only releases within the range >=12.0.0 <13.0.0 can be merged into the maintenance branch 12.x and published to the 12.x distribution channel.

The branch 12.x head should be reset to a previous commit so the commit with tag 14.0.2 is removed from the branch history.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot :package::rocket:

github-actions[bot] commented 1 year ago

:rotating_light: The automated release from the 12.x 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 12.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 14.0.1 on branch 12.x cannot be published as it is out of range.

Only releases within the range >=12.0.0 <13.0.0 can be merged into the maintenance branch 12.x and published to the 12.x distribution channel.

The branch 12.x head should be reset to a previous commit so the commit with tag 14.0.1 is removed from the branch history.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot :package::rocket:

github-actions[bot] commented 1 year ago

:rotating_light: The automated release from the 12.x 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 12.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 14.0.0 on branch 12.x cannot be published as it is out of range.

Only releases within the range >=12.0.0 <13.0.0 can be merged into the maintenance branch 12.x and published to the 12.x distribution channel.

The branch 12.x head should be reset to a previous commit so the commit with tag 14.0.0 is removed from the branch history.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot :package::rocket:

github-actions[bot] commented 1 year ago

:rotating_light: The automated release from the 12.x 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 12.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 12.3.1 on branch 12.x cannot be published as it is out of range.

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

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 12.x with git revert or git reset.

A valid branch could be master.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot :package::rocket: