Support for Deployer v8 (deployer/deployer ^8.0)

[konradmichalik]

Summary

composer.json currently pins deployer/deployer: ^7.0.0, which prevents using deployer-extended together with the recently released Deployer v8 (latest v8.0.5). I'd like to ask whether v8 support is planned, and to offer help with the upgrade.

Background

Deployer v8 was released as a stable major (v8.0.0 … v8.0.5). The headline changes are MAML recipes and improved error output, but the public API used by recipe libraries appears largely unchanged — recipe/common.php and the core functions (set, get, has, run, runLocally, task, desc, parse, currentHost, invoke, etc.) all still exist in v8.0.5`.

The main impact for deployer-extended is in the dependency constraints, not the recipe code itself.

What changes in v8 (from deployer/deployer v8.0.5 composer.json)

Requirement	v7	v8
php	^8.0 | ^7.3	^8.3
symfony/console	^6 || ^7	^7.4.0 || ^8.0.0
symfony/process	–	^7.4.0 || ^8.0.0
symfony/yaml	–	^7.4.0 || ^8.0.0
maml/maml	–	^3.2 (new)

So a v8-compatible release of deployer-extended would likely need to:

1. Widen the constraint to deployer/deployer: ^7.0.0 || ^8.0.0 (or a separate major that targets ^8.0 only).
2. Raise the minimum PHP version to ^8.3 if v8-only, or keep it compatible with both lines if a single release should support v7 and v8.
3. Verify the bundled recipes against v8 (the API surface looks stable, but a smoke test of the full deploy flow would confirm it).

Question

• Is v8 support on the roadmap?
• Would you prefer a combined ^7 || ^8 constraint, or a new major dedicated
  to v8?

[kszymukowicz]

hi @konradmichalik

Tnx for bringing this up. Support for v8 is of course planned.
Plz check the new release 24.2.0. It works well on my testing environment.