v0.7.0

Adopts sandermuller/boost-core ^0.6. boost-core 0.6.0 retired its Composer plugin, so the composer boost:* subcommands move to the standalone vendor/bin/boost binary and auto-sync on composer install becomes an opt-in callback you wire into your own project. package-boost-php itself remains a Composer plugin — its package-boost-php:lean and package-boost-php:gitattributes commands are unaffected.

Also widens symfony/console and symfony/process to permit symfony 8 (Laravel 13).

See UPGRADING.md for the full 0.6 → 0.7 migration.

Breaking changes

• Requires sandermuller/boost-core ^0.6. boost-core 0.6.0 retired its Composer plugin:

  • The composer boost:* subcommands are gone — run them through the standalone binary instead (the boost: prefix is dropped):

    Was	Now
    composer boost:install	vendor/bin/boost install
    composer boost:sync	vendor/bin/boost sync
    composer boost:doctor	vendor/bin/boost doctor
    composer boost:tags	vendor/bin/boost tags

  • Auto-sync on composer install is no longer automatic. To keep composer install re-syncing, wire the callback into your own project's composer.json:

    "scripts": {
        "post-install-cmd": ["SanderMuller\\BoostCore\\Scripts\\BoostAutoSync::run"],
        "post-update-cmd": ["SanderMuller\\BoostCore\\Scripts\\BoostAutoSync::run"]
    }

    A dependency's post-install-cmd does not fire in a consuming project — only the root package's scripts run — so this must live in your composer.json. Otherwise, run vendor/bin/boost sync yourself (e.g. in CI). BOOST_SKIP_AUTOSYNC=1 disables the callback.

  • Optionally drop the now-dead sandermuller/boost-core entry from your config.allow-plugins — boost-core is no longer a plugin. Composer ignores the stale entry, so leaving it is harmless.

Changed

• Widened symfony/console and symfony/process to ^7.0||^8.0. ^7.0 alone excluded symfony 8 (Laravel 13); the widen unblocks installation on those projects. package-boost-laravel inherits the cap transitively, so the widen lifts it for the whole package-boost line.

Fixed

• 0.6.0's release notes / README had ->withTags(['boost-extension']) — that array form passes an array into a variadic Tag|string ...$tags parameter and fatals with a TypeError on boost.php load. The correct call is variadic: ->withTags('boost-extension'). Both files are corrected in this release; if you copied the array form from 0.6.0's notes into your boost.php, switch it.

Full Changelog: 0.6.0...0.7.0