v0.18.0
Breaking — sandermuller/boost-core floor raised to ^0.20
The sandermuller/boost-core constraint narrows from ^0.18 || ^0.19
to ^0.20, dropping support for boost-core 0.18 and 0.19.
boost-core 0.20 makes the BoostConfig builder methods array-typed. The
withTags() variadic form fatals on 0.20, and the new array form fatals
on 0.18/0.19 — the two styles cannot be expressed compatibly in a single
boost.php, so the floor moves to 0.20 in lockstep.
If your composer.json requires boost-core below ^0.20, bump it:
composer require sandermuller/boost-core:^0.20withTags() is now array-typed
Update your boost.php (or .config/boost.php) to pass an array:
- ->withTags(
- Tag::Php,
- 'release-automation',
- );
+ ->withTags([
+ Tag::Php,
+ 'release-automation',
+ ]);Only withTags() callers using the variadic form need the change —
withAgents(), withAllowedVendors(), withExcludedSkills(),
withRemoteSkills(), and withConventions() already took arrays. See
UPGRADING.md
for the full note.
Changed
minimum-stabilityset tostable(wasdev), with
prefer-stable: trueunchanged. No dependency requires dev stability.
No source/API changes — the package's public surface is unchanged. This
release is constraint and configuration only.
Full Changelog: 0.17.0...0.18.0