Skip to content

chore(deps): replace laminas-config-aggregator with webware-configmanager - #67

Merged
tyrsson merged 1 commit into
1.0.xfrom
tyrsson-swap-configmanager
Nov 17, 2026
Merged

tyrsson merged 1 commit into
1.0.xfrom
tyrsson-swap-configmanager

Conversation

@tyrsson

@tyrsson tyrsson commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

Mechanical swap

laminas/laminas-config-aggregator is replaced by webware/webware-configmanager ^1.0.0-alpha.4.

The replacement is a drop-in: the constructor takes the same arguments in the same order,
getMergedConfig() returns the same array, and ArrayProvider and PhpFileProvider have direct
equivalents. Parity is already covered by webware-configmanager's
test/integration/LaminasConfigAggregatorParityTest.php, so this pull request does not re-prove it.

Touch points:

  • composer.json: the requirement is swapped.
  • config/config.php: ArrayProvider, ConfigAggregator and PhpFileProvider imports. Provider
    list, its order and its comments are unchanged.
  • config/autoload/global.php: ConfigAggregator::ENABLE_CACHE becomes ConfigCache::ENABLE_CACHE.
  • config/development.config.php.dist: the same constant. dev:mode --enable copies this file to
    config/development.config.php, which config/config.php aggregates, so leaving the Laminas
    reference there would throw a class-not-found as soon as development mode is enabled.
  • test/integration/Application/CommandRegistrationIntegrationTest.php: the two imports only, no
    behavioural change.

No wrapper, adapter or shim was added, and no gate was given a baseline or suppression entry.

Forced lock movement

webware-configmanager requires brick/varexporter ^0.7.0. laminas/laminas-servicemanager 4.5.1
requires brick/varexporter ^0.3.8 || ^0.4.0 || ^0.5.0 || ^0.6.0, so it cannot stay. Measured, not
assumed:

$ composer require laminas/laminas-servicemanager:4.5.1 --dry-run
    - laminas/laminas-servicemanager 4.5.1 requires brick/varexporter ^0.3.8 || ^0.4.0 || ^0.5.0 || ^0.6.0
      -> found brick/varexporter[0.3.8, 0.4.0, 0.5.0, 0.6.0] but the package is fixed to 0.7.0
Your requirements could not be resolved to an installable set of packages.

Every lock entry that moved, and whether it was forced:

Package From To Forced
brick/varexporter 0.6.0 0.7.0 Yes, required by webware-configmanager
laminas/laminas-config-aggregator 1.20.0 removed Yes, this swap
laminas/laminas-servicemanager 4.5.1 4.6.0 Yes, 4.5.1 caps varexporter at ^0.6.0
webimpress/safe-writer 2.2.0 removed Yes, it was a dependency of laminas-config-aggregator
webware/webware-configmanager absent 1.0.0-alpha.4 Yes, this swap
webware/webware-filewriter absent 1.0.0-alpha.2 Yes, required by webware-configmanager
php-standard-library/type absent 6.4.2 Yes, required by webware-configmanager
php-standard-library/file absent 6.4.2 Yes, via webware-filewriter
php-standard-library/filesystem absent 6.4.2 Yes, via webware-filewriter
php-standard-library/collection absent 6.4.2 Yes, via the php-standard-library dependency chain

Nothing else moved. The lock was produced with composer update ... --minimal-changes, and a full
composer update was discarded because it also re-resolved unrelated packages.

php-standard-library/* did not move from require-dev to require: php-standard-library/terminal
was already a runtime requirement, and type, file, filesystem and collection arrive as
transitive runtime dependencies.

Gates

  • phpunit: 147 tests, 8 failures. All 8 are in DevelopmentModeCommandTest and reproduce on the
    unmodified baseline in this Windows checkout (symlink creation and CRLF expectations), so they are
    not caused by this change and were not touched.
  • mago analyze: no issues.
  • mago guard: no issues.
  • mago lint: no issues in the touched files. 71 warnings exist repo-wide, all in files this change
    does not touch.
  • mago format --check: the touched files are formatted. Two other files repo-wide are not, and they
    are unformatted on the baseline too.
  • Config cache both ways: with ENABLE_CACHE => true, php bin/webware list writes
    data/cache/config-cache.php. With config/development.config.php in place, the same command
    writes no cache file.

Follow-up

webware-configmanager supports #[LoadAfter] and #[LoadBefore] for provider ordering. Not
adopted here, because this pull request keeps the provider list exactly as it was. Adopting them is a
separate change.

CI

The Continuous Integration run is fully green on this head: Mago (PHP 8.4), Mago (PHP 8.5),
Test (PHP 8.4 and 8.5, each on latest, locked and lowest), Mutation testing, Codecov and
codecov/patch.

…ager

The aggregator is a drop-in replacement: the constructor takes the same
arguments in the same order and getMergedConfig() returns the same array, so
only the imports move. The provider list and its order are unchanged.

Forced lock movement: webware-configmanager requires brick/varexporter ^0.7.0
and laminas/laminas-servicemanager 4.5.1 caps varexporter at ^0.6.0, so
servicemanager moves to 4.6.0.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@codecov

codecov Bot commented Nov 17, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@tyrsson
tyrsson merged commit a8abce8 into 1.0.x Nov 17, 2026
12 checks passed
@tyrsson
tyrsson deleted the tyrsson-swap-configmanager branch November 17, 2026 00:25
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.

1 participant