#Drupal CMS stable release blocker

The idea was to allow recipes to install node module with a text_long body field, but recipes can already do that since they skip installing module config. So yeah this doesn't do anything, we need 📌 Remove node_add_body_field from NodeTypeForm Active instead. Closing as duplicate of the other two isseus.

If that's for Drupal CMS and not for every installation, why not to use separate `node/config/install` sub-folder that will install the relevant config?

I don't think that changes much in practice so far, if it doesn't have dependencies that might not be fullfilled, still going to be always installed?

If it's optional, we need to change node_add_body_field() to return early if the field doesn't exist and document that it might return null, which is a bit of an API change?

Okay - I merged !213, and will tag beta1 from that, but that's not the end of this issue. Let's deal with the rest of the dependencies/patches in subsequent MRs in this issue.

Already deleteable via the API, just not via the UI.

@phenaproxima MR!213 contains the switch to tagged releases for ECA, bpmn_io and Klaro.