Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The automated release is failing 🚨 #1704

Closed
nockbot opened this issue Sep 4, 2019 · 3 comments
Closed

The automated release is failing 🚨 #1704

nockbot opened this issue Sep 4, 2019 · 3 comments
Labels
semantic-release

Comments

@nockbot
Copy link
Collaborator

nockbot commented Sep 4, 2019

🚨 The automated release from the undefined 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 undefined 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 12.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 >=11.3.2 <12.0.0 can be published from branch master.

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 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 📦🚀
@mastermatt
Copy link
Member

@gr2m not sure why nockbot was trying to release a 12.0, thoughts?

@gr2m
Copy link
Member

gr2m commented Sep 5, 2019

wow no idea ... for reference, this is the build that failed:
https://travis-ci.org/nock/nock/jobs/580909609

I'm looking into it

@nockbot nockbot closed this as completed Sep 5, 2019
@gr2m
Copy link
Member

gr2m commented Sep 5, 2019

My fault, I created the wrong tag to fix the release from master before. It should be all good now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
semantic-release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gr2m @mastermatt @nockbot