PR Checklist
Please check if your PR fulfills the following requirements:
- [x] The commit message follows our guidelines: https://github.com/graycoreio/github-actions-magento2/blob/main/CONTRIBUTING.md#commit
- [ ] Tests for the changes have been added (for bug fixes / features)
- [ ] Docs have been added / updated (for bug fixes / features)
PR Type
What kind of change does this PR introduce?
- [ ] Bugfix
- [ ] Feature
- [ ] Code style update (formatting, local variables)
- [ ] Refactoring (no functional changes, no api changes)
- [ ] Build related changes
- [x] CI related changes
- [ ] Documentation content changes
- [ ] Other... Please describe:
What is the current behavior?
Nightly builds initialize the required php infra with
- name: Set PHP version
uses: shivammathur/setup-php@v2
with:
php-version: ${{ inputs.php-version }}
tools: composer:v${{ inputs.composer-version }}
coverage: none
The value for inputs.composer-version
is 2
.
This currently pulls in composer 2.4.2
.
However, the result is a broken upstream nightly and mageos nightly build. When composer install is run while determining the base package dependencies, it fails with the error:
- laminas/laminas-dependency-plugin 2.5.0 requires composer-plugin-api >=1.1.0 <2.3.0
-> found composer-plugin-api[2.3.0] but it does not match the constraint.
What is the new behavior?
This MR changes the value for inputs.composer-version
to 2.2
.
This installs a compatible composer version.
Does this PR introduce a breaking change?
Other information
Reference