The automated release is failing 🚨

owilliams320 commented 1 month ago

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

Based on the releases published on other branches, only versions within the range >=8.14.2 can be published from branch release/4.16.x.

The following commits are responsible for the invalid release:

fix(test): release (47d2b878)
fix(markdown): allow relative paths (#2182) (1d2938b7)
fix(icon): update to use material icons outline (#2160) (4256ec43)
fix: add v4 branch to release pipeline (9a0fc632)
ci: add 4.x release branch (422ad6ad)
feat: add raw code toggle to highlight component and update theme (fe0fbc2a)

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

A valid branch could be main or release/4.16.x.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot :package::rocket:

owilliams320 commented 1 month ago

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

Based on the releases published on other branches, only versions within the range >=8.14.2 can be published from branch release/4.x.x.

The following commits are responsible for the invalid release:

fix(icon): update to use material icons outline (#2160) (4256ec43)
fix: add v4 branch to release pipeline (9a0fc632)
ci: add 4.x release branch (422ad6ad)
feat: add raw code toggle to highlight component and update theme (fe0fbc2a)

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

A valid branch could be main or release/4.x.x.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot :package::rocket:

owilliams320 commented 1 month ago

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

Based on the releases published on other branches, only versions within the range >=8.14.2 can be published from branch release/4.x.x.

The following commits are responsible for the invalid release:

fix(markdown): allow relative paths (#2191) (36933f3c)
fix(icon): update to use material icons outline (#2160) (4256ec43)
fix: add v4 branch to release pipeline (9a0fc632)
ci: add 4.x release branch (422ad6ad)
feat: add raw code toggle to highlight component and update theme (fe0fbc2a)

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

A valid branch could be main or release/4.x.x.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot :package::rocket:

Teradata / covalent