2.4.9 Compatability

[tim-breitenstein-it]

Hi!

Is there is a version 2.4.9 compatibility in the pipeline?

$ composer require magento/data-migration-tool:2.4.9

  Problem 1
    - Root composer.json requires magento/data-migration-tool 2.4.9 (exact version match: 2.4.9 or 2.4.9.0), found magento/data-migration-tool[2.0.0, ..., 2.4.8.1] but it does not match the constraint.

$ composer require magento/data-migration-tool

Problem 1
    - Root composer.json requires magento/data-migration-tool * -> satisfiable by magento/data-migration-tool[2.0.0, ..., 2.4.8.1].
    - magento/data-migration-tool[2.0.0, ..., 2.1.9] require symfony/console ~2.3 -> found symfony/console[v2.3.0, ..., v2.8.52] but the package is fixed to v7.4.14 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - magento/data-migration-tool[2.2.0, ..., 2.2.7] require symfony/console ~2.3, !=2.7.0 -> found symfony/console[v2.3.0, ..., v2.8.52] but the package is fixed to v7.4.14 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - magento/data-migration-tool[2.3.0, ..., 2.3.3] require symfony/console ~4.1.0 -> found symfony/console[v4.1.0, ..., v4.1.12] but the package is fixed to v7.4.14 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - magento/data-migration-tool[2.3.4, ..., 2.3.5] require symfony/console ~4.1.0||~4.2.0||~4.3.0||~4.4.0 -> found symfony/console[v4.1.0, ..., v4.4.49] but the package is fixed to v7.4.14 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - magento/data-migration-tool[2.4.0, ..., 2.4.5] require symfony/console ~4.4.0 -> found symfony/console[v4.4.0, ..., v4.4.49] but the package is fixed to v7.4.14 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - magento/data-migration-tool[2.4.6, ..., 2.4.6.1] require symfony/console ^5.4 -> found symfony/console[v5.4.0, ..., v5.4.47] but the package is fixed to v7.4.14 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - magento/data-migration-tool[2.4.7, ..., 2.4.8.1] require symfony/console ^6.4 -> found symfony/console[v6.4.0, ..., v6.4.42] but the package is fixed to v7.4.14 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require magento/data-migration-tool:*" to figure out if any version is installable, or "composer require magento/data-migration-tool:^2.1" if you know which you need.

THX

[m2-assistant]

Hi @tim-breitenstein-it. Thank you for your report.
To speed up processing of this issue, make sure that you provided sufficient information.
Add a comment to assign the issue: @magento I am working on this

---

Join Magento Community Engineering Slack and ask your questions in #github channel.