The code style issue reported is not related to this change.

yeah, the requested CS change is because the new rule regarding namespacing constants has been deployed in fabbot, but the new version of the fixer has not yet been applied on the project code.

How does this play with flex when it needs to add entries to .env files?
I suppose you patched your public/index.php and bin/console files accordingly?
A better option might provided by symfony/symfony#38465, which manages an "extra.runtime.dotenv_path" for this.

Indeed, I've manually changed the .env filename in public/index.php, bin/console, and .gitignore, but then I got stuck because I couldn't tell dump-env to dump the new .env files for production.

This approach definitely breaks flex by writing to the wrong .env file. But it's not a blocking issue, as I can always copy the generated lines and move them in the correct place.

And, of course, if the new symfony/runtime component allows configuring the .env filename everywhere (including the dump env command), then it's definitely a nicer approach than what I'm trying to do here.

Should I close this PR?