Allow configuring the core_version_requirement of features per bundle

It would be maybe just nice if once the .info.yml file was written initially, if it didn't attempt to update that line afterwards, or only if it matches the previous value that was set by the module.

It would be maybe just nice if once the .info.yml file was written initially, if it didn't attempt to update that line afterwards, or only if it matches the previous value that was set by the module.

Agreed. I think this is the correct business logic. The current logic is problematic when, say, a Features module has been made compatible for the next major version of Drupal while the site is still running on a previous version. Another simple way of stating the proposed business logic change is "If a module already has a core_version_requirement set, don't try to change it." This would be different than this issue title's stated goal of allowing configuration, but would also avoid the stated B/C breaking consideration.

The merge request proposes to change the logic to "If a module already has a core_version_requirement set, don't try to change it."