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

Closed
github-actions bot opened this issue Jun 27, 2024 · 1 comment
Closed

The automated release is failing 🚨 #110

github-actions bot opened this issue Jun 27, 2024 · 1 comment
Labels
semantic-release

Comments

@github-actions
Copy link

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

Based on the releases published on other branches, only versions within the range >=4.0.3 can be published from branch v4-dev.

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 v4-dev with git revert or git reset.

A valid branch could be main or v4-dev.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀
@github-actions GitHub Actions
Copy link
Author

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

Based on the releases published on other branches, only versions within the range >=4.0.3 can be published from branch v4-dev.

The following commits are responsible for the invalid release:

  • fix(ci): empty commit so semantic-release shuts up BREAKING CHANGE: v4 release (8cb7c27)
  • chore(ci): empty commit so semantic-release shuts up (c440fa7)
  • chore(ci): empty commit so semantic-release shuts up (4e4859d)
  • chore(ci): empty commit so semantic-release shuts up (9579c41)
  • chore(ci): add v4-dev to release branches (4dd6afd)
  • chore(ci): return of the CI (b092d49)
  • fix(*): fixes for jun 26 beta (7e0cb15)
  • fix(package): unbreak react (b1e5038)
  • chore(package): v4.0.3 (832ad69)
  • fix(package): pin react properly (62b454f)
  • fix(package): fix ts memes (ea19d62)
  • fix(Menu): work around ConfigContext error (9f26209)
  • fix(components): forgot one (e6e8c91)
  • fix(components): fix missing children prop also remove unnessecary use of tsx (688c747)
  • chore(ci): disable on v4 for now (6c1b12b)
  • chore(release): 3.26.1 [CI SKIP] (0dfb2ce)
  • fix(Field): add children prop (2a78cc0)
  • chore(package): ver bump [skip ci] (1716782)
  • fix(plugin): shim definePlugin for now [ci skip] (0cd498b)
  • chore(plugin): delete (b728d90)
  • chore(*): fix version lol (3384d29)
  • chore(release): 3.26.0 [CI SKIP] (78c4cdb)
  • chore(releaserc): add v4-dev branch (d20659e)
  • fix(utils/react): shut it ts (d91f49e)
  • chore(*): init v4 package.json and release.yaml (735080f)
  • chore(static-classes): add/fix/update css classes (chore(static-classes): add/fix/update css classes #102) (86e6e4c)
  • Dropdown contextMenuPositionOptions prop definition (Dropdown contextMenuPositionOptions prop definition #104) (46b1d6e)
  • chore(*): run prettier (a7635b6)
  • feat(*): add v4 webpack api and port everything to it also restructures a bunch (bffd530)
  • chore(package): init v4 (9c79187)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch v4-dev with git revert or git reset.

A valid branch could be main or v4-dev.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

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
0 participants