-
-
Notifications
You must be signed in to change notification settings - Fork 9.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] Help fade out "composer/package-versions-deprecated" #44726
Comments
Given that Symfony 6 requires composer 2, we can use the native API in our own packages |
For doctrine pacjages, this should be discussed with the doctrine team though |
Doctrine DBAL 3.3 will require Composer 2 and drop the dependency: doctrine/dbal#5078 |
OK, then I guess it is fine for other Doctrine projects to do the same kind of change @nicolas-grekas I updated the packagist URL to list only packages having a require constraint. |
Symfony packages are using it for 2 purposes:
|
…poser/package-versions-deprecated (stof) This PR was merged into the 4.4 branch. Discussion ---------- [ProxyManagerBridge] Remove the unused dependency on composer/package-versions-deprecated | Q | A | ------------- | --- | Branch? | 4.4 | Bug fix? | yes/no | New feature? | no <!-- please update src/**/CHANGELOG.md files --> | Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files --> | Tickets | - | License | MIT | Doc PR | n/a The ProxyManagerBridge depends on friendsofphp/proxy-manager-lts which has an optional dependency on the PackageVersions class to implement the `ProxyManager\Version::getVersion` method on composer 1 (with a fallback to a less precise version number). However, the bridge has stopped using that API in favor of feature detection (in #39017), so the dependency is unused. This contributes to #44726 Commits ------- 6ca8e30 Remove the unused dependency on composer/package-versions-deprecated
…precated (stof) This PR was merged into the 5.3 branch. Discussion ---------- Remove direct dependency on composer/package-versions-deprecated | Q | A | ------------- | --- | Branch? | 5.3 | Bug fix? | no | New feature? | no | Deprecations? | no | Tickets | n/a | License | MIT | Doc PR | n/a This dependency in the doctrine-bridge was added to enforce the replacement of the ocramius/package-versions package used by the ORM, to keep support for PHP versions we needed. But as of 2.7.4, the ORM switched its dependency, so this is not necessary anymore. This contributes to #44726 Commits ------- c106a6b Remove direct dependency on composer/package-versions-deprecated
I think we can close here, thank you all for the help! |
…ated (stof) This PR was merged into the main branch. Discussion ---------- Remove the dependency on composer/package-versions-deprecated This package was added in the past to force keeping support for composer 1 when using doctrine/orm. In the meantime, doctrine/orm has switched to using that package directly, making this root requirement useless. And in the next releases of doctrine/orm and doctrine/dbal, they are migrating to use composer-runtime-api (dropping support for composer 1) instead of using this plugin, as part of the effort to fade out that compat plugin. Refs symfony/symfony#44726 The package is still present for now (and so still needed in the list of allowed plugins too) because doctrine packages require it. But this will change in their next releases for DBAL, ORM and Migrations (the PRs are already merged) Commits ------- f12bb2c Remove the dependency on composer/package-versions-deprecated
…ated (stof) This PR was merged into the main branch. Discussion ---------- Remove the dependency on composer/package-versions-deprecated This package was added in the past to force keeping support for composer 1 when using doctrine/orm. In the meantime, doctrine/orm has switched to using that package directly, making this root requirement useless. And in the next releases of doctrine/orm and doctrine/dbal, they are migrating to use composer-runtime-api (dropping support for composer 1) instead of using this plugin, as part of the effort to fade out that compat plugin. Refs symfony/symfony#44726 The package is still present for now (and so still needed in the list of allowed plugins too) because doctrine packages require it. But this will change in their next releases for DBAL, ORM and Migrations (the PRs are already merged) Commits ------- f12bb2c Remove the dependency on composer/package-versions-deprecated
…ated (stof) This PR was merged into the main branch. Discussion ---------- Remove the dependency on composer/package-versions-deprecated This package was added in the past to force keeping support for composer 1 when using doctrine/orm. In the meantime, doctrine/orm has switched to using that package directly, making this root requirement useless. And in the next releases of doctrine/orm and doctrine/dbal, they are migrating to use composer-runtime-api (dropping support for composer 1) instead of using this plugin, as part of the effort to fade out that compat plugin. Refs symfony/symfony#44726 The package is still present for now (and so still needed in the list of allowed plugins too) because doctrine packages require it. But this will change in their next releases for DBAL, ORM and Migrations (the PRs are already merged) Commits ------- f12bb2c Remove the dependency on composer/package-versions-deprecated
Discussed with @Seldaek on Slack: it'd be great if we could help fade out this package by not requiring it in either
symfony/*
ordoctrine/*
. Instead, we should use the API provided by Composer 2.Let's start from the most downloaded packages as listed here:
https://packagist.org/packages/composer/package-versions-deprecated/dependents?order_by=downloads&requires=require
The text was updated successfully, but these errors were encountered: