twittwer / nx-tools

Workspace for Nx Plugins.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

The automated release is failing 🚨

github-actions opened this issue Β· comments

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

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 resolve 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 is 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 1.4.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 >=1.3.2 <1.4.0 can be published from branch master.

The following commits are responsible for the invalid release:

  • docs(compodoc): add watch mode recipe with storybook integration (a516ce8)
  • feat(compodoc): add watch mode (#21) (a5e0218)
  • chore: update @type/node to latest LTS 12.19.1 (#20) (d3d5981)
  • Merge pull request #18 from twittwer/dependabot/npm_and_yarn/http-proxy-1.18.1 (d96fb0b)
  • Merge pull request #17 from twittwer/dependabot/npm_and_yarn/elliptic-6.5.3 (a9a82f5)
  • build(deps): bump http-proxy from 1.18.0 to 1.18.1 (0943931)
  • build(deps): bump elliptic from 6.5.2 to 6.5.3 (b012ead)

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 πŸ“¦πŸš€