FEATURE: Enable migration Version20251005080230 which adjusts EEL in Fusion code to the new Neos 9 API

[mhsdesign]

Adjustment after the upmerge of #5638 for 9.0

This is a step of the process to remove the fusion migration task from neos/rector. People who already updated via the neos/rector migrations or already are on Neos 9.0 will find this migration obsolete - though we cannot recognise that and thus the migration will be run on the package never-the-less if executed via ./flow flow:core:migrate

To especially prevent these new fusion migrations from being run they have to be manually excluded before running flow:core:migrate by modifying the composer.json to include:

{
    "extra": {
        "applied-flow-migrations": [
            // ...
            "Neos.Neos-20251005080230",
            "Neos.Fusion-20251006080506"
        ]
    }
}

Users already on 9.0 might need to exclude the fusion migrations when updating to this patch as there could be false positive detections when using ${item.label} or ${item.identfier} in Fusion which is found by this migration as possible unsafe. The migration recognises that the variable item could be node which would require manual adjustments and thus the migration adds a todo comment to the file. These todo comments then might be totally obsolete for people already on a working 9.0.

Upgrade instructions

Review instructions

The command neos9preparation:preadjustfusion from Neos 8.4 was removed as flow:core:migrate Neos.Demo --version 20251005080230 is now its successor

Checklist

• Code follows the PSR-2 coding style
• Tests have been created, run and adjusted as needed
• The PR is created against the lowest maintained branch
• Reviewer - PR Title is brief but complete and starts with FEATURE|TASK|BUGFIX
• Reviewer - The first section explains the change briefly for change-logs
• Reviewer - Breaking Changes are marked with !!! and have upgrade-instructions

[mhsdesign]

Denny and me agreed that we want to add these 3 migration files retroactively to Neos 9 via patch release as even running the core migrations on an existing running 9.0 project should not do any harm. And migrations are run explicitly under supervision of a developer:)

• Version20251005080230 rewrite fusion node access and helpers ${node.identifier} -> enabled via this change FEATURE: Enable migration Version20251005080230 which adjusts EEL in Fusion code to the new Neos 9 API #5642 (*)
• Version20251006080506 rewrite removed fusion prototypes Neos.Fusion:Collection etc (already part of 8.4 and upmerged)
• Version20251109115127 rewrite yaml (previously "YamlDimensionConfigRector" and "YamlRoutePartHandlerRector") FEATURE: Add yaml Flow core Neos 9 migrations (previously in rector) #5680

(*) it could happen that a false positive todo comment is written to fusion files but thats it :)
If there are no objections to this month old monolog discussion id like to continue with that:)