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 🚨 #831

Closed
github-actions bot opened this issue Apr 7, 2023 · 19 comments
Closed

The automated release is failing 🚨 #831

github-actions bot opened this issue Apr 7, 2023 · 19 comments
Labels
semantic-release Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR

Comments

@github-actions
Copy link
Contributor

github-actions bot commented Apr 7, 2023

🚨 The automated release from the main 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 main 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 10.8.0 on branch main cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=10.7.0 <10.7.1 can be published from branch main.

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 main 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 📦🚀
@wolfy1339 wolfy1339 added the Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR label Apr 7, 2023
@wolfy1339
Copy link
Member

😓 This is because of tests rolled in the next branch as part of #819

@oscard0m
Copy link
Member

oscard0m commented Apr 7, 2023

😓 This is because of tests rolled in the next branch as part of #819

What tests? @wolfy1339

@wolfy1339
Copy link
Member

The test releases we made

@oscard0m
Copy link
Member

oscard0m commented Apr 7, 2023 •
edited
Loading

The steps to follow are:

  1. PR reverting this commit: revert(typescript): new pull_request.milestoned and pull_request.demilestoned events (#830)" #833
  2. merge next branch: merge next #834
  3. PR to restore the reverted commit in 1.

Would you like for me to take that? @wolfy1339

@wolfy1339
Copy link
Member

Go ahead

@github-actions
Copy link
Contributor Author

github-actions bot commented Apr 7, 2023

🚨 The automated release from the main 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 main 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 10.8.0 on branch main cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=10.7.0 <10.7.1 can be published from branch main.

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 main 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 📦🚀

@github-actions
Copy link
Contributor Author

🚨 The automated release from the main 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 main 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 10.8.0 on branch main cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=10.7.0 <10.7.1 can be published from branch main.

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 main 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 📦🚀

@wolfy1339
Copy link
Member

@oscard0m I'm going to try to merge main into next

@gr2m @kfcampbell @nickfloyd Can one of you help merge the branch next into main

@kfcampbell
Copy link
Member

@wolfy1339 do you want #834 or #835 to go in?

@wolfy1339
Copy link
Member

wolfy1339 commented Apr 10, 2023 •
edited
Loading

@wolfy1339 do you want #834 or #835 to go in?

#834

It has to be a standard merge commit, and not a rebase or squash in order to get the proper release flow

@oscard0m
Copy link
Member

@wolfy1339 isn't #835 more updated? I see you did some changes there 2 hours ago.

@wolfy1339
Copy link
Member

Yes, you are correct.
#835 is the correct one

Merging next into main

@oscard0m
Copy link
Member

Closed #834 to avoid confusion

@kfcampbell
Copy link
Member

kfcampbell commented Apr 10, 2023 •
edited
Loading

Alright! Confirming one more time before merging: #835 is ready to go now, with a regular merge commit, correct?

@wolfy1339
Copy link
Member

Yes, merging #835 with a regular merge commit

@wolfy1339
Copy link
Member

@oscard0m I un-reverted #830 (reverted #833) in next. That way we don't need a PR for it, and it will be done already. It will already be released

Once it's merged in main, it'll get pushed to the @latest tag, and un-marked as a pre-release on GitHub

@kfcampbell
Copy link
Member

Done! Merge commits weren't enabled on the repo, so I temporarily enabled them before merging. Please let me know if I should do anything else here!

@oscard0m
Copy link
Member

@wolfy1339 Do you know what's missing to have the releases up to date?

@wolfy1339
Copy link
Member

I'm not sure. Let's try an empty commit to trigger a release

@wolfy1339 wolfy1339 mentioned this issue Apr 12, 2023
Merged
5 tasks
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 Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@oscard0m @wolfy1339 @kfcampbell