Description
🚨 The automated release from the release-6.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-6.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 6.5.3 on branch release-6.x.x cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=6.5.2 <6.4.0 can be published from branch release-6.x.x.
The following commits are responsible for the invalid release:
- fix: Security upgrade follow-redirects from 1.15.5 to 1.15.6 (refactor: Security upgrade follow-redirects from 1.15.5 to 1.15.6 #9019) (422958e)
- ci: Fix LTS releases are published as pre-releases (ci: Fix LTS releases are published as pre-releases #8989) (b8535b3)
- ci: Fix failing Docker release by removing arm/v6 and arm/v7 support (ci: Fix failing Docker release by removing arm/v6 and arm/v7 support #8977) (9282bc5)
- refactor: Upgrade graphql-list-fields from 2.0.2 to 2.0.4 (refactor: Upgrade graphql-list-fields from 2.0.2 to 2.0.4 #8973) (47184f0)
- refactor: Upgrade winston-daily-rotate-file from 4.7.1 to 5.0.0 (refactor: Upgrade winston-daily-rotate-file from 4.7.1 to 5.0.0 #8974) (d53c1f3)
Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch release-6.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 📦🚀