Skip to content

Conversation

@abdounikarim
Copy link

Q A
Branch? main for features / current stable version branch for bug fixes
Tickets Closes #..., closes #...
License MIT
Doc PR api-platform/docs#...

Hello API Platform team,

It seems the actual app is not working.
You can reproduce the case by:

  1. Cloning the current project
  2. Building images: docker compose build --no-cache --pull
  3. Starting containers: docker compose up --wait

The php container is unhealthy and showing we need to update php dependencies by running: composer update.
Update fails even with composer update -W.
This command show:

Loading composer repositories with package information
Restricting packages listed in "symfony/symfony" to "7.2.*"
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires symfony/security-bundle 7.2.* -> satisfiable by symfony/security-bundle[v7.2.0, ..., v7.2.9].
    - symfony/security-bundle[v7.2.0, ..., v7.2.9] require symfony/http-foundation ^6.4|^7.0 -> found symfony/http-foundation[v6.4.0, ..., v6.4.31, v7.0.0, ..., v7.4.3] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
  Problem 2
    - Root composer.json requires symfony/twig-bundle 7.2.* -> satisfiable by symfony/twig-bundle[v7.2.0, v7.2.8, v7.2.9].
    - symfony/twig-bundle[v7.2.0, ..., v7.2.9] require symfony/http-foundation ^6.4|^7.0 -> found symfony/http-foundation[v6.4.0, ..., v6.4.31, v7.0.0, ..., v7.4.3] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
  Problem 3
    - Root composer.json requires api-platform/symfony ^4.2.11 -> satisfiable by api-platform/symfony[v4.2.11, v4.2.12].
    - api-platform/metadata[v4.2.7, ..., v4.2.12] require symfony/type-info ^7.3 || ^8.0 -> found symfony/type-info[v7.3.0, ..., v7.4.1, v8.0.0, v8.0.1] but these were not loaded, likely because it conflicts with another require.
    - api-platform/metadata[v4.1.19, ..., v4.2.6] require symfony/type-info ^7.3 -> found symfony/type-info[v7.3.0, ..., v7.4.1] but these were not loaded, likely because it conflicts with another require.
    - api-platform/symfony[v4.2.11, ..., v4.2.12] require api-platform/metadata ^4.2.3 -> satisfiable by api-platform/metadata[v4.2.3, ..., v4.2.12].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Looking on packagist, it seems the api-platform/metadata package : https://packagist.org/packages/api-platform/metadata has a dependency symfony/type-info with 7.3|8.0version.

Upgrading all symfony dependencies fixes the error and app starting without errors.

@Chris53897
Copy link
Contributor

Chris53897 commented Jan 15, 2026

Updated. Sorry i missed that this is an PR and not an issue.
I think this should be updated to 7.4 or 8.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants