magento / magento/composer-root-update-plugin
should not trigger warning during install from composer.lock
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 59
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
as with direct download including a hash its already protected enough
// just reporting as I saw multiple reports in various chats triggered by the new release of magento/composer
reported here, because thats the repository linked from https://magento.com/blog/best-practices/adobe-releases-new-composer-plugin-magento-243-release
if its belonging into a different, please advise/forward
(does it belong to https://github.com/magento/composer-dependency-version-audit-plugin ?)
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 by reproducing the warning during installation from composer.lock and compare it with a direct download that includes a hash. The issue names no source file or test, so first identify which install path emits the warning and confirm that the warning is absent when the locked package is already protected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100