Add support for Payum 2.0

[pierredup]

Summary

Makes the bundle work against both payum/core 1.x and 2.0. Which one is installed is detected at compile time and the services which differ are loaded accordingly, so nothing has to change in an application to keep running on 1.x.

The interesting difference in 2.0 is that Payum builds every gateway with a dependency injection container. The bundle hands it the application's services as the global container, which is what lets a service of the application be injected into the constructor of an action.

How the version is detected

PayumVersion::supportsDependencyInjection() asks interface_exists(ContainerConfiguration::class) rather than reading Composer's metadata. payum/payum replaces payum/core, and neither declares a version outside of a release, so a development install reports a version that says nothing about which APIs are present. The DI interfaces added in 2.0 do.

Changes

• Service config split — the services which differ between generations move to Resources/config/payum_v1.php and payum_v2.php; PayumExtension loads one or the other.

• PayumCoreGatewayFactory — implements Payum\Core\DI\ContainerConfiguration and takes the place of ContainerAwareCoreGatewayFactory / CoreGatewayFactoryBuilder on 2.0. Replacing payum.core_gateway_factory_builder with your own still works; it now has to build a factory implementing ContainerConfiguration.

• New payum.global_service tag — shares an application service with Payum. The optional id attribute names it, which is how a service is shared under the interface an action type-hints:

  services:
      App\Payment\ExchangeRates:
          tags:
              - { name: payum.global_service, id: App\Payment\ExchangeRatesInterface }

• Existing tags keep working — payum.action, payum.api and payum.extension keep the same attributes. A tagged service now reaches a gateway as an entry of its container rather than as an "@id" string resolved at runtime, so the alias attribute no longer names anything and is ignored.

• Gateway factories that predate ContainerConfiguration — still every factory payum/core ships — are built the way they were in 1.x, and payum/core triggers a deprecation for them.

• composer.json — payum/core widened to ^1.7.2 || ^2.0.

• UPGRADE.md — documents all of the above under a "Payum 2.0" heading.

Tests

New coverage in PayumCoreGatewayFactoryTest, PayumVersionTest, Tests/DI/SymfonyContainerAdapterTest, BuildGlobalContainerPassTest, and a functional PayumV2Test booting the kernel with config_payum_v2.yml.

The CI matrix gains payum: 2.x legs which swap the sub-package dev requirements for payum/payum:2.x-dev — the gateways became part of the monorepo in 2.0, so they cannot be installed alongside it.

Note on the second commit

14b4233 skips the autowiring test when the installed payum/core cannot be told a container lists its entries. That was needed while ListableContainerInterface was still unmerged; it landed in Payum/Payum#1046, so on 2.x-dev the guard no longer trips and the test asserts for real. The skip stays for anyone running the suite against a payum/core without it.

Running the suite locally against payum/core 1.x skips the 2.0-specific tests as designed — the payum: 2.x CI legs are what exercise the new paths.

🤖 Generated with Claude Code

https://claude.ai/code/session_01ARB2EkkjTiRA2WvJjgwteU

---

Generated by Claude Code

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.