The automated release is failing 🚨,about dhis2/data-visualizer-app

dhis2-bot commented on June 20, 2024

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

Based on the releases published on other branches, only versions within the range >=36.0.0 <35.20.20 can be published from branch 36.x.

The following commits are responsible for the invalid release:

Merge branch 'master' into 36.x (43c4842)
Merge branch 'master' into 36.x (9242a27)
fix(translations): sync translations from transifex (36.x) (#1660) (592a44f)
Merge branch 'master' into 36.x (c6ea81f)
chore(release-prepare): branch 36.x (7afe4b9)

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

A valid branch could be 32.x, 33.x, 34.x, 35.x or master.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

from data-visualizer-app.

dhis2-bot commented on June 20, 2024

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

Based on the releases published on other branches, only versions within the range >=36.0.0 <35.20.20 can be published from branch 36.x.

The following commits are responsible for the invalid release:

feat: bump major BREAKING CHANGE: no breaking changes (caef855)
Merge branch 'master' into 36.x (43c4842)
Merge branch 'master' into 36.x (9242a27)
fix(translations): sync translations from transifex (36.x) (#1660) (592a44f)
Merge branch 'master' into 36.x (c6ea81f)
chore(release-prepare): branch 36.x (7afe4b9)

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

A valid branch could be master.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

from data-visualizer-app.

dhis2-bot commented on June 20, 2024

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

Based on the releases published on other branches, only versions within the range >=36.0.0 <35.20.20 can be published from branch 36.x.

The following commits are responsible for the invalid release:

Merge branch 'master' into 36.x (43c4842)
Merge branch 'master' into 36.x (9242a27)
fix(translations): sync translations from transifex (36.x) (#1660) (592a44f)
Merge branch 'master' into 36.x (c6ea81f)
chore(release-prepare): branch 36.x (7afe4b9)

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

A valid branch could be 32.x, 33.x, 34.x, 35.x or master.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

from data-visualizer-app.

dhis2-bot commented on June 20, 2024

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

Based on the releases published on other branches, only versions within the range >=36.0.0 <35.20.20 can be published from branch 36.x.

The following commits are responsible for the invalid release:

feat: set version 36.0.0 (#1677) (79021e9)
Merge branch 'master' into 36.x (43c4842)
Merge branch 'master' into 36.x (9242a27)
fix(translations): sync translations from transifex (36.x) (#1660) (592a44f)
Merge branch 'master' into 36.x (c6ea81f)
chore(release-prepare): branch 36.x (7afe4b9)

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

A valid branch could be master.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

from data-visualizer-app.

The automated release is failing 🚨 about data-visualizer-app HOT 4 CLOSED

Comments (4)

🚨 The automated release from the `36.x` branch failed. 🚨

The release `35.20.20` on branch `36.x` cannot be published as it is out of range.

🚨 The automated release from the `36.x` branch failed. 🚨

The release `36.0.0` on branch `36.x` cannot be published as it is out of range.

🚨 The automated release from the `36.x` branch failed. 🚨

The release `35.20.20` on branch `36.x` cannot be published as it is out of range.

🚨 The automated release from the `36.x` branch failed. 🚨

The release `36.0.0` on branch `36.x` cannot be published as it is out of range.

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

Comments (4)

🚨 The automated release from the 36.x branch failed. 🚨

The release 35.20.20 on branch 36.x cannot be published as it is out of range.

🚨 The automated release from the 36.x branch failed. 🚨

The release 36.0.0 on branch 36.x cannot be published as it is out of range.

🚨 The automated release from the 36.x branch failed. 🚨

The release 35.20.20 on branch 36.x cannot be published as it is out of range.

🚨 The automated release from the 36.x branch failed. 🚨

The release 36.0.0 on branch 36.x cannot be published as it is out of range.

Related Issues (20)

Recommend Projects

Recommend Topics

Recommend Org

🚨 The automated release from the `36.x` branch failed. 🚨

The release `35.20.20` on branch `36.x` cannot be published as it is out of range.

🚨 The automated release from the `36.x` branch failed. 🚨

The release `36.0.0` on branch `36.x` cannot be published as it is out of range.

🚨 The automated release from the `36.x` branch failed. 🚨

The release `35.20.20` on branch `36.x` cannot be published as it is out of range.

🚨 The automated release from the `36.x` branch failed. 🚨

The release `36.0.0` on branch `36.x` cannot be published as it is out of range.