Conversation
…adjust content-hash
There was a problem hiding this comment.
Pull request overview
Updates this Composer plugin’s metadata and dependency constraints in preparation for a v3.0.0 release and broader Symfony support.
Changes:
- Update package description to reflect lowercase
modules/<name>install path. - Broaden
symfony/finderandsymfony/processconstraints to allow Symfony^7.0or^8.0.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "symfony/finder": "^7.0|^8.0", | ||
| "symfony/process": "^7.0|^8.0" |
There was a problem hiding this comment.
composer.json requirements were changed, but composer.lock is still pinned to the old content-hash. Since CI runs composer validate, this will fail unless composer.lock is regenerated (e.g., composer update --lock or update these packages with --lock).
| "symfony/finder": "^7.0|^8.0", | ||
| "symfony/process": "^7.0|^8.0" |
There was a problem hiding this comment.
This PR claims Symfony 7 compatibility by broadening the constraint, but the committed lockfile (and CI) will still test against Symfony 8 only. Consider adding CI coverage for a Symfony 7 install (e.g., a job that updates symfony/finder + symfony/process to the latest 7.x allowed by the constraint and runs the PHPUnit suite) to ensure the new supported range is actually verified.
No description provided.