Great! Seems like the releases notes for v7.1 to v7.2 are much shorter than the v7.0 to v7.1 update!!

I tried the happy paths and it worked well:

1. updating an existing development_app from develop (v7.1) to this branch (v7.2)
2. creating a new development_app

Both of these work.

I'll give you some feedback on missing things that we should do. We can do them in another PR if you want, but I'm leaving this in one place so I don't miss them, as they're lots of small things:

• update @rails/ujs to latest compatible version: https://www.npmjs.com/package/@rails/ujs/v/7.1.501 (there isn't a 7.2 version as far as I see)
• update @rails/activestorage to latest compatible version: https://www.npmjs.com/package/@rails/activestorage/v/7.2.201
• add the new_framework_defaults_7_2.rb file, so we have the backlog for the next PR (changing defaults from 7.1 to 7.2)
• while reading about this update, I found out about the change with the development secrets that we talked in #13267. I'd recommend renaming the file in our Releases Notes:

  decidim/RELEASE_NOTES.md

  Line 81 in 5cea8a4

  ⚠ **Important**: Local environment variable introduced

• while reading the Releases Notes, I saw that we're mentioning that implementers should remove the decidim initializer

  decidim/RELEASE_NOTES.md

  Line 38 in 5cea8a4

  git rm config/initializers/decidim.rb

  but we're still generating it for new apps. We should remove that from the generator
• another pending thing related to the Env Vars/initailizer/secrets change is this clean-up #14446

As I mentioned, I'm ok with merging this as is (as long as you agree with removing these https://github.com/decidim/decidim/pull/14784/files#r2126005712 😄), and do the other changes in other PRs, as they're slightly related to the v7.2 change but as the pipeline is green and the happy path work correctly, then I don't want to block this

Merging this as I'm OK with the current status.

I created an issue to keep track of the pending changes: #14804