Comments (5)
π¨ 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 25.0.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 >=24.0.2 <24.1.0
can be published from branch main
.
The following commits are responsible for the invalid release:
- feat!: Updated build child products job type. Updated PcmJobBase type (#869) (eb2bbf0)
- feat: subs product price units (#871) (1d3c5ea)
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 beta
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
from js-sdk.
π¨ 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 25.0.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 >=24.0.2 <24.1.0
can be published from branch main
.
The following commits are responsible for the invalid release:
- Revert "feat: subs product price units (#871)" (#874) (23d020d)
- feat!: Updated build child products job type. Updated PcmJobBase type (#869) (eb2bbf0)
- feat: subs product price units (#871) (1d3c5ea)
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 beta
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
from js-sdk.
π¨ 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 25.0.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 >=24.0.2 <24.1.0
can be published from branch main
.
The following commits are responsible for the invalid release:
- fix: subs product price units (#875) (10e2f66)
- Revert "feat: subs product price units (#871)" (#874) (23d020d)
- feat!: Updated build child products job type. Updated PcmJobBase type (#869) (eb2bbf0)
- feat: subs product price units (#871) (1d3c5ea)
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 beta
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
from js-sdk.
π¨ 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 25.0.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 >=24.0.2 <24.1.0
can be published from branch main
.
The following commits are responsible for the invalid release:
- Revert "feat!: Updated build child products job type. Updated PcmJobBase type (#869)" (#873) (146d6fd)
- fix: subs product price units (#875) (10e2f66)
- Revert "feat: subs product price units (#871)" (#874) (23d020d)
- feat!: Updated build child products job type. Updated PcmJobBase type (#869) (eb2bbf0)
- feat: subs product price units (#871) (1d3c5ea)
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 beta
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
from js-sdk.
π¨ 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 25.0.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 >=24.0.2 <24.1.0
can be published from branch main
.
The following commits are responsible for the invalid release:
- feat!: Build child products return type update (#876) (1cb64e7)
- Revert "feat(types): added signatures for application keys rps limit" (d06cebc)
- feat(types): added signatures for application keys rps limit (20ba793)
- Revert "feat!: Updated build child products job type. Updated PcmJobBase type (#869)" (#873) (146d6fd)
- fix: subs product price units (#875) (10e2f66)
- Revert "feat: subs product price units (#871)" (#874) (23d020d)
- feat!: Updated build child products job type. Updated PcmJobBase type (#869) (eb2bbf0)
- feat: subs product price units (#871) (1d3c5ea)
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 beta
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π
from js-sdk.
Related Issues (20)
- Action Required: Fix Renovate Configuration
- "TypeError: MoltinGateway is not a function" HOT 1
- Flows One-To-Many relationship doesn't accept array as body HOT 1
- Dependency Dashboard
- PCM products/productId/nodes endpoint response HOT 1
- Return type is wrong for `CreateCart` method in `src/types/cart.d.ts`
- Regression on the Config class behavior HOT 1
- Issues with Order and AddressBase types not matching the order data from get order response HOT 2
- Question: Filter by custom fileds HOT 1
- Type issue with "hierarchies" / "hierarchy_id" and the GET /catalog response HOT 3
- Fetch throttling support with http keepalive HOT 1
- Passing currency/language headers to addProductToCart function.
- Missing `target_attributes` field for promotions `schema` type HOT 1
- Not able to access GetProductsByHierarchy endpoint
- relationships property missing on FieldBase type
- TypeScript errors when skipLibCheck is false
- ESM-Support for node
- Incorrect type of order property in FieldBase
- Adding product to cart from another catalog says "Product not found" HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from js-sdk.