Skip to content

The automated release is failing 🚨 #9555

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom
Closed
parseplatformorg opened this issue Jan 16, 2025 · 3 comments
Closed

The automated release is failing 🚨 #9555

parseplatformorg opened this issue Jan 16, 2025 · 3 comments
Labels
type:ci CI related issue

Comments

@parseplatformorg
Copy link
Contributor

🚨 The automated release from the release-7.x.x branch failed. 🚨

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

Based on the releases published on other branches, only versions within the range >=7.4.0 <7.4.0 can be published from branch release-7.x.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 release-7.x.x with git revert or git reset.

A valid branch could be release.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀
@parse-github-assistant Parse GitHub Assistant
Copy link

The label semantic-release cannot be used here.

@parse-github-assistant Parse GitHub Assistant
Copy link

Thanks for opening this issue!

@parseplatformorg
Copy link
Contributor Author

🚨 The automated release from the release-7.x.x branch failed. 🚨

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

Based on the releases published on other branches, only versions within the range >=7.4.0 <7.4.0 can be published from branch release-7.x.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 release-7.x.x with git revert or git reset.

A valid branch could be release.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
type:ci CI related issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@parseplatformorg