github-actions[bot]
commented
20 hours ago :rotating_light: The automated release from the master 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 master 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 18.0.0 on branch master cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=17.8.2 <18.0.0 can be published from branch master.
The following commits are responsible for the invalid release:
- Merge pull request #187 from US-EPA-CAMD/revert-185-feature/6421-update_nestjs_dependencies (add9b9f)
- Revert "Feature/6421 update nestjs dependencies" (22d52b1)
- Merge pull request #185 from US-EPA-CAMD/feature/6421-update_nestjs_dependencies (16fa678)
- Merge branch 'master' into feature/6421-update_nestjs_dependencies (53246bb)
- revert(6421): restored a package resolution specification (95e7299)
- chore(6421)!: updated NestJS dependencies (c3291cd)
- Merge pull request #182 from US-EPA-CAMD/dependabot/npm_and_yarn/cross-spawn-7.0.6 (89a819b)
- chore(deps): bump cross-spawn from 7.0.3 to 7.0.6 (27a4ff2)
Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch master with git revert or git reset.
A valid branch could be next.
See the workflow configuration documentation for more details.
Good luck with your project ✨
Your semantic-release bot :package::rocket:
:rotating_light: The automated release from the
masterbranch 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
masterbranch. 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
18.0.0on branchmastercannot be published as it is out of range.Based on the releases published on other branches, only versions within the range
>=17.8.2 <18.0.0can be published from branchmaster.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
masterwith git revert or git reset.A valid branch could be
next.See the workflow configuration documentation for more details.
Good luck with your project ✨
Your semantic-release bot :package::rocket: