magento / magento/magento-cloud
Constraints for Cloud Metapackage
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 226
- Forks
- 244
- PR merge metrics
- No merged PRs in 30d
Description
## Description
The constraint numbers for the metapackage don't need to be set as : >=current_version =2.3.4 <2.3.5"`
This is because the Cloud metapackage require does this -
```
"require": {
"fastly/magento2": "^1.2.34",
"magento/ece-tools": "^2002.1.0",
"magento/module-paypal-on-boarding": "~100.4.0",
"magento/product-enterprise-edition": ">=2.4.2 <2.4.3"
},
```
## Possible solutions
Change `"magento/magento-cloud-metapackage":">=2.x.y <2.x.z"` to `"magento/magento-cloud-metapackage":"2.x.y"` in composer.json
There is an issue on DEVDOCS for the docs - https://github.com/magento/devdocs/issues/9094
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the relevant composer.json entry for magento/magento-cloud-metapackage and compare its constraint with the Cloud metapackage requirements shown in the issue. Done means the constraint uses the specified 2.x.y form rather than a current-to-next-version range; the linked DevDocs issue provides related context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100