Skip to content

Add back RectorConfig::tag() as a no-op BC layer - #8431

Merged
TomasVotruba merged 1 commit into
mainfrom
bc-restore-tag-noop
Sep 2, 2026
Merged

Add back RectorConfig::tag() as a no-op BC layer#8431
TomasVotruba merged 1 commit into
mainfrom
bc-restore-tag-noop

Conversation

@TomasVotruba

Copy link
Copy Markdown
Member

Fixes rectorphp/rector#9880

The DI container switch to entropy (#8362) dropped the tag() method that used to be inherited from illuminate/container. Configs and sets that still call ->tag() now blow up with:

Call to undefined method Rector\Config\RectorConfig::tag()

even when the project never calls it directly (a set does).

This restores tag() as a deprecated no-op. Tagging is not needed anymore - the entropy container discovers services by contract - so the call is simply accepted and ignored to keep BC.

https://claude.ai/code/session_01SPWpEgoaHa33ypRUWccHHr

The DI container switch to entropy removed the tag() method inherited
from illuminate/container. Older configs and sets still call it, causing
"Call to undefined method Rector\Config\RectorConfig::tag()". Restore it
as a deprecated no-op, since services are now discovered by contract.

Claude-Session: https://claude.ai/code/session_01SPWpEgoaHa33ypRUWccHHr
@TomasVotruba
TomasVotruba merged commit c8f5dae into main Sep 2, 2026
44 checks passed
@TomasVotruba
TomasVotruba deleted the bc-restore-tag-noop branch September 2, 2026 09:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Undefined method Rector\Config\RectorConfig::tag() when upgrading from 2.6.3 to 2.6.4

1 participant