nestjs-relay icon indicating copy to clipboard operation
nestjs-relay copied to clipboard

The automated release is failing 🚨

Open github-actions[bot] opened this issue 3 years ago • 2 comments

: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 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 4.1.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 >=4.0.4 <4.1.0 can be published from branch master.

The following commits are responsible for the invalid release:

  • feat: add async mutation support (#217) (b7f34ac)
  • chore(deps): update dependency husky to v4.3.8 (#186) (de24bbc)
  • chore(deps): update dependency apollo-server-express to v2.19.2 (#182) (5605e70)
  • chore: update package lock (309293a)
  • Merge branch 'master' of github.com:rogerballard/nestjs-relay (aebd092)
  • chore(deps): update dependency lint-staged to v10.5.3 (#187) (c92b150)
  • chore(deps): update coverallsapp/github-action action to v1.1.2 (#180) (f95e8b1)
  • chore(deps): update dependency class-validator to v0.13.1 (#183) (01d33ac)
  • chore(deps): update dependency prettier to v2.2.1 (#188) (58b697b)
  • chore(deps): update dependency semantic-release to v17.3.7 (#190) (84ce537)
  • chore(deps): update dependency typedoc-neo-theme to v1.1.0 (#194) (f754eb3)
  • chore(deps): update dependency typescript to v4.1.3 (#195) (9604ded)
  • chore(deps): update nest monorepo to v7.6.11 (#196) (f94d360)
  • chore(docs): remove incomplete docs (5e27b73)
  • chore(deps): update actions/setup-node action to v2 (#197) (e8c57ec)
  • build(renovate): configure auto merging rules (60e4d8b)
  • chore(deps): update dependency commitizen to v4.2.3 (#184) (6edf115)
  • chore(deps): update dependency rollup to v2.38.4 (#189) (bd2af8d)
  • chore(deps): update dependency ts-jest to v26.5.0 (#191) (79825b4)
  • chore(deps): update dependency typedoc to v0.20.20 (#192) (27c0635)

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:

github-actions[bot] avatar Apr 15 '21 16:04 github-actions[bot]

: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 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 4.1.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 >=4.0.4 <4.1.0 can be published from branch master.

The following commits are responsible for the invalid release:

  • chore: fix failed build (e27df38)
  • feat: add async mutation support (#217) (b7f34ac)
  • chore(deps): update dependency husky to v4.3.8 (#186) (de24bbc)
  • chore(deps): update dependency apollo-server-express to v2.19.2 (#182) (5605e70)
  • chore: update package lock (309293a)
  • Merge branch 'master' of github.com:rogerballard/nestjs-relay (aebd092)
  • chore(deps): update dependency lint-staged to v10.5.3 (#187) (c92b150)
  • chore(deps): update coverallsapp/github-action action to v1.1.2 (#180) (f95e8b1)
  • chore(deps): update dependency class-validator to v0.13.1 (#183) (01d33ac)
  • chore(deps): update dependency prettier to v2.2.1 (#188) (58b697b)
  • chore(deps): update dependency semantic-release to v17.3.7 (#190) (84ce537)
  • chore(deps): update dependency typedoc-neo-theme to v1.1.0 (#194) (f754eb3)
  • chore(deps): update dependency typescript to v4.1.3 (#195) (9604ded)
  • chore(deps): update nest monorepo to v7.6.11 (#196) (f94d360)
  • chore(docs): remove incomplete docs (5e27b73)
  • chore(deps): update actions/setup-node action to v2 (#197) (e8c57ec)
  • build(renovate): configure auto merging rules (60e4d8b)
  • chore(deps): update dependency commitizen to v4.2.3 (#184) (6edf115)
  • chore(deps): update dependency rollup to v2.38.4 (#189) (bd2af8d)
  • chore(deps): update dependency ts-jest to v26.5.0 (#191) (79825b4)
  • chore(deps): update dependency typedoc to v0.20.20 (#192) (27c0635)

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:

github-actions[bot] avatar May 04 '21 16:05 github-actions[bot]

: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 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 4.1.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 >=4.0.4 <4.1.0 can be published from branch master.

The following commits are responsible for the invalid release:

  • build: trigger major version bump (931c951)
  • chore: fix failed build (e27df38)
  • feat: add async mutation support (#217) (b7f34ac)
  • chore(deps): update dependency husky to v4.3.8 (#186) (de24bbc)
  • chore(deps): update dependency apollo-server-express to v2.19.2 (#182) (5605e70)
  • chore: update package lock (309293a)
  • Merge branch 'master' of github.com:rogerballard/nestjs-relay (aebd092)
  • chore(deps): update dependency lint-staged to v10.5.3 (#187) (c92b150)
  • chore(deps): update coverallsapp/github-action action to v1.1.2 (#180) (f95e8b1)
  • chore(deps): update dependency class-validator to v0.13.1 (#183) (01d33ac)
  • chore(deps): update dependency prettier to v2.2.1 (#188) (58b697b)
  • chore(deps): update dependency semantic-release to v17.3.7 (#190) (84ce537)
  • chore(deps): update dependency typedoc-neo-theme to v1.1.0 (#194) (f754eb3)
  • chore(deps): update dependency typescript to v4.1.3 (#195) (9604ded)
  • chore(deps): update nest monorepo to v7.6.11 (#196) (f94d360)
  • chore(docs): remove incomplete docs (5e27b73)
  • chore(deps): update actions/setup-node action to v2 (#197) (e8c57ec)
  • build(renovate): configure auto merging rules (60e4d8b)
  • chore(deps): update dependency commitizen to v4.2.3 (#184) (6edf115)
  • chore(deps): update dependency rollup to v2.38.4 (#189) (bd2af8d)
  • chore(deps): update dependency ts-jest to v26.5.0 (#191) (79825b4)
  • chore(deps): update dependency typedoc to v0.20.20 (#192) (27c0635)

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:

github-actions[bot] avatar May 04 '21 16:05 github-actions[bot]