search

patternfly / react-topology

MIT License
12 stars 19 forks source link

The automated release is failing 🚨 #253

Open github-actions[bot] opened 3 hours ago

github-actions[bot] commented 3 hours ago

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

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

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

A valid branch could be do-not-delete.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot :package::rocket:

github-actions[bot] commented 3 hours ago

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

Based on the releases published on other branches, only versions within the range >=5.4.1 <4.93.4 can be published from branch v5.

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

A valid branch could be do-not-delete.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot :package::rocket: