magento / magento/composer-root-update-plugin
For v2.0 : Composer::Version can not detect the version number from certain composer version strings
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 59
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Certain composer version will cause the Composer::VERSION to be empty
/usr/local/bin/composer --version
Composer version **2.6-dev+4e1774518002b0be4365fe62ce220b2011c2b4bf (2.6-dev)** 2023-03-29 09:32:46
Magento/ComposerRootUpdatePlugin/updater/RootPackageRetriever :: findBestCandidate() -- code logic will go into the else block, the Composer::VERSION is empty
Contributor guide
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 at Magento/ComposerRootUpdatePlugin/updater/RootPackageRetriever::findBestCandidate() and trace how the shown Composer 2.6-dev+4e1774518002b0be4365fe62ce220b2011c2b4bf (2.6-dev) string is handled. Confirm the expected Composer::VERSION value and verify that it is no longer empty for this version format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100