symplify/monorepo-builder

What's Changed

Features

• Add parameterized disableAutoloadMerge(sections, forTypes) API — independently control which composer.json autoload sections (autoload, autoload-dev) get skipped from root merge, optionally filtered by package type. New Symplify\MonorepoBuilder\Config\AutoloadSection and Symplify\MonorepoBuilder\Config\PackageType enums power the API; mixing enum cases and plain strings in the same call is supported (escape hatch for composer/installers ecosystem types like wordpress-plugin, drupal-module, symfony-bundle, and for user-defined custom types). Multiple types are OR-matched. Two filter channels are intentionally distinct: pass forTypes: [] to skip every package regardless of type; pass a non-empty list to skip ONLY packages whose composer.json declares the matching type literally. (#117)
• New query methods MBConfig::shouldSkipAutoload(?string $packageType): bool and MBConfig::shouldSkipAutoloadDev(?string $packageType): bool let custom mergers consult the configured rules per package. The bundled AutoloadComposerKeyMerger and AutoloadDevComposerKeyMerger now consult them symmetrically. (#117)

Deprecations

• The zero-argument form MBConfig::disableAutoloadMerge() continues to work but now emits an E_USER_DEPRECATED notice. It maps to skipping both sections for all packages — equivalent to disableAutoloadMerge(sections: [AutoloadSection::Autoload, AutoloadSection::AutoloadDev], forTypes: []). Update existing config files at your convenience.
• MBConfig::isAutoloadMergeDisabled() getter is marked @deprecated; prefer shouldSkipAutoload($packageType) and shouldSkipAutoloadDev($packageType) for new code.

Full Changelog: 12.6.2...12.7.0

Honor disablePackageReplace() in RootRemoveComposerJsonDecorator (#116)

Fix repositories array becoming a JSON object after path-type dedup (…

Add disablePackageReplace() and disableAutoloadMerge() opt-outs for n…

What's Changed

Bug Fixes

• Remove stale composer-json-manipulator autoload entry that breaks PHAR build (#109)
• Fix workers() not respecting user-specified order (#112)

Improvements

• Allow sebastian/diff ^8 (#110)

Full Changelog: 12.5.0...12.5.2

Remove stale composer-json-manipulator autoload entry that breaks PHA…

What's Changed

Bug Fixes

• Merge command now preserves unknown/custom composer.json sections — Sections like scripts-aliases, abandoned, readme, and any other non-standard keys in root composer.json are no longer silently dropped during merge (#105, #106)
• dataToAppend supports arbitrary composer.json keys — No longer limited to the 24 hardcoded sections (#105)
• Original section order of root composer.json is preserved by default — New sections are appended at the end; custom ordering is available via composerSectionOrder() (#107)
• Fix comparator transitivity violations in ComposerJson::sortItemsByOrderedListOfKeys() and ArraySorter::recursiveSortBySchema()
• Fix FilterOutDuplicatedRequireAndRequireDevJsonDecorator which was a no-op due to array_intersect comparing values instead of keys
• Fix self-merge bug in MergedAndDecoratedComposerJsonFactory (was merging object with itself)

Improvements

• Allow webmozart/assert ^2 (#103)

Internal

• Consolidate require/require-dev dedup logic into ComposerJsonMerger and decorator
• Add explicit DECORATOR_ORDER constant for decorator execution ordering
• Remove dead code: RequireRequireDevDuplicateCleaner, src-deps/composer-json-manipulator/

Full Changelog: 12.4.5...12.5.0

Fix disableDefaultWorkers() edge case where user-added workers were i…