Tags: palantirnet/drupal-rector
Tags
feat: remove RemoveAliasManagerCacheMethodCallsRector (#418) AliasManager::setCacheKey() and AliasManager::writeCache() became no-ops in 11.3.0, when the path alias preload cache was replaced by the Fiber-based bulk-lookup strategy. Removing the call therefore reclaims nothing but a lost micro-optimization, and because drupal-rector defaults to minimumCoreVersionSupported 10.1.0 with BC enabled, the default output was a DeprecationHelper::backwardsCompatibleCall() wrapper around a no-op. The four contrib call sites don't make the case either: redirect already hand-fixed with its own `instanceof AliasManager && version_compare(...)` guard — the rector would wrap that a second time domain_path AliasManagerInterface decorators; the matched line domain_unique_path_alias is their own forwarding call, which must keep forwarding until removal in 13.0.0 seo_urls own SeoUrlManager, excluded by the type guard Removes the rector, its two test classes and fixtures, the 11.3 deprecation set registration, and the coverage-registry entry. The digest record is marked skip so rector-discover does not resurface it. Note for upgrade_status: DeprecationAnalyzer::isRectorCovered() still hardcodes both messages, so it will keep reporting them as rector-covered until that list is updated upstream. Reported by catch in #415
docs: prepare 1.1.0 release and backfill missing 1.0.1 section (#409) - Add retroactive [1.0.1] section for the composer-based sets bootstrap fix (#404), which was tagged 2026-07-02 but never documented. - Move the RemoveAliasManagerCacheMethodCallsRector fix and the new AddSymfonyConstraintValidatorTypeDeclarationsRector into a [1.1.0] section dated today; leave [Unreleased] empty. - Fix the broken [#3600790] reference link (inline the full GitLab URL).
PreviousNext