Deprecated trigger behaviour option in use

After upgrade to 2026.7, the following warning is received:

Deprecated trigger behaviour option in use
Warning · Reported by Home Assistant Core Integration
This stops working in version 2027.1. Please address before upgrading.
An automation, script or template entity uses the trigger behavior option any, which has been renamed to each. The old value still works for now, but support for it will be removed in a future release.

To fix this issue, open each affected automation or script in the editor and save it again; Home Assistant will automatically detect and update the deprecated option. Alternatively, edit your configuration files (for example automations.yaml) directly and change behavior: any to behavior: each. Restart Home Assistant afterwards.

In an attempt to fix, I edited automations.yaml and found/replaced these entries. After that the affected automations are 'broken', and in the editor I can see no way to 'fix' them. So I reverted the change in automations.yaml.

If instead I open each affected automation in the editor as the warning suggests, HA doesn't offer any way to automatically 'fix' anything, nor can I see a way to fix it myself.

I can see there are at least two others having this issue from the release blog post. What is the recommended approach on this please, and is there some issue preventing HA from offering the fix?

If I manually attempt the recommended edit within just one of the automations, I get the following error:

"Message malformed: value must be one of ['all', 'any'] for dictionary value @ data['options']['behavior']"

As such it seems that the renamed value of 'behavior: each' is not even valid!

Same here ...

I also have 3 automations with this issue. Editing the yaml and making the suggested change breaks the automation. The error says only any, all are valid values; not each

open a bug report on Github

I have 12 automations that have this 'problem', but if you change from any to each I get the same error - it expects any or all. This needs addressing before 2026.7.1