dhis2 / data-visualizer-app Goto Github PK
View Code? Open in Web Editor NEWDHIS2 Data Visualizer App
License: BSD 3-Clause "New" or "Revised" License
DHIS2 Data Visualizer App
License: BSD 3-Clause "New" or "Revised" License
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.
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:
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 π¦π
35.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 35.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.
35.12.25
on branch 35.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=35.12.24 <35.12.25
can be published from branch 35.x
.
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 35.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
35.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 35.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.
35.12.25
on branch 35.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=35.12.24 <35.12.25
can be published from branch 35.x
.
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 35.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
33.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 33.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.
32.1.0
on branch 33.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=33.0.0 <34.0.0
can be published from branch 33.x
.
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 33.x
with git revert or git reset.
A valid branch could be 33.x
, 34.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
35.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 35.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.
35.12.25
on branch 35.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=35.12.24 <35.12.25
can be published from branch 35.x
.
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 35.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
39.x
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 39.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 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.
39.2.10
on branch 39.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=39.2.9 <39.2.10
can be published from branch 39.x
.
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 39.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
, 35.x
, 36.x
, 37.x
, 38.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
master
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 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 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 App Hub application id must be defined in d2.config.js
Good luck with your project β¨
Your semantic-release bot π¦π
33.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 33.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.
32.1.0
on branch 33.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=33.0.0 <34.0.0
can be published from branch 33.x
.
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 33.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
33.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 33.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.
32.1.0
on branch 33.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=33.0.0 <34.0.0
can be published from branch 33.x
.
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 33.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
34.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 34.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.
35.0.0
on branch 34.x
cannot be published as it is out of range.Only releases within the range >=34.0.0 <35.0.0
can be merged into the maintenance branch 34.x
and published to the 34.x
distribution channel.
The branch 34.x
head should be reset to a previous commit so the commit with tag v35.0.0
is removed from the branch history.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
39.x
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 39.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 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.
39.2.10
on branch 39.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=39.2.9 <39.2.10
can be published from branch 39.x
.
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 39.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
, 35.x
, 36.x
, 37.x
, 38.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
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.
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 <36.0.0
can be published from branch 36.x
.
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 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 π¦π
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.
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:
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 π¦π
As of #327 it overflows the bottom edge of the page. This should be fixed in the shell and correctly inherited by the app.
33.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 33.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.
32.1.0
on branch 33.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=33.0.0 <34.0.0
can be published from branch 33.x
.
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 33.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
35.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 35.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.
35.12.25
on branch 35.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=35.12.24 <35.12.25
can be published from branch 35.x
.
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 35.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
35.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 35.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.
35.12.25
on branch 35.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=35.12.24 <35.12.25
can be published from branch 35.x
.
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 35.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
33.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 33.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.
32.1.0
on branch 33.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=33.0.0 <34.0.0
can be published from branch 33.x
.
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 33.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
35.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 35.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.
35.12.25
on branch 35.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=35.12.24 <35.12.25
can be published from branch 35.x
.
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 35.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
38.x
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 38.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 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.
38.2.2
on branch 38.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=38.2.1 <38.2.2
can be published from branch 38.x
.
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 38.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
, 35.x
, 36.x
, 37.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
Dependabot couldn't authenticate with registry.npmjs.org.
You can provide authentication details in your Dependabot dashboard by clicking into the account menu (in the top right) and selecting 'Config variables'.
35.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 35.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.
35.12.25
on branch 35.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=35.12.24 <35.12.25
can be published from branch 35.x
.
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 35.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
33.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 33.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.
32.1.0
on branch 33.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=33.0.0 <34.0.0
can be published from branch 33.x
.
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 33.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
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.
35.20.16
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.16
can be published from branch 36.x
.
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 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 π¦π
35.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 35.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.
35.12.25
on branch 35.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=35.12.24 <35.12.25
can be published from branch 35.x
.
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 35.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
35.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 35.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.
35.12.25
on branch 35.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=35.12.24 <35.12.25
can be published from branch 35.x
.
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 35.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
38.x
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 38.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 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.
38.2.2
on branch 38.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=38.2.1 <38.2.2
can be published from branch 38.x
.
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 38.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
, 35.x
, 36.x
, 37.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
master
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 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 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 App Hub application id must be defined in d2.config.js
Good luck with your project β¨
Your semantic-release bot π¦π
39.x
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 39.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 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.
39.2.10
on branch 39.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=39.2.9 <39.2.10
can be published from branch 39.x
.
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 39.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
, 35.x
, 36.x
, 37.x
, 38.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
33.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 33.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.
32.1.0
on branch 33.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=33.0.0 <34.0.0
can be published from branch 33.x
.
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 33.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
39.x
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 39.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 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.
39.2.10
on branch 39.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=39.2.9 <39.2.10
can be published from branch 39.x
.
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 39.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
, 35.x
, 36.x
, 37.x
, 38.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
33.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 33.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.
32.1.0
on branch 33.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=33.0.0 <34.0.0
can be published from branch 33.x
.
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 33.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
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.
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 <36.0.0
can be published from branch 36.x
.
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 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 π¦π
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.
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.19
can be published from branch 36.x
.
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 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 π¦π
39.x
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 39.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 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.
39.2.10
on branch 39.x
cannot be published as it is out of range.Based on the releases published on other branches, only versions within the range >=39.2.9 <39.2.10
can be published from branch 39.x
.
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 39.x
with git revert or git reset.
A valid branch could be 32.x
, 33.x
, 34.x
, 35.x
, 36.x
, 37.x
, 38.x
or master
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
A declarative, efficient, and flexible JavaScript library for building user interfaces.
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. πππ
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google β€οΈ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.