The automated release is failing π¨
github-actions opened this issue Β· 0 comments
π¨ The automated release from the master
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 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 5.2.2
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 >=5.2.1 <5.2.2
can be published from branch master
.
The following commits are responsible for the invalid release:
- build(deps): bump ovsx from 0.5.1 to 0.5.2 (#347) (5c94e27)
- fix: use context's cwd for vsce calls (#349) (86b499e)
- fix: make sure to use locally installed
vsce
(#348) (6d18e32) - build(deps-dev): bump @commitlint/cli from 17.1.2 to 17.2.0 (#352) (5f949bb)
- build(deps-dev): bump @commitlint/config-conventional (#351) (f8b16d1)
- build(deps-dev): bump eslint-plugin-n from 15.3.0 to 15.4.0 (#350) (a56f765)
- build(deps-dev): bump ava from 4.3.3 to 5.0.1 (#345) (c17e38e)
- build(deps-dev): bump eslint from 8.25.0 to 8.26.0 (#346) (e469aa8)
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 π¦π