I'm not sure if this is a good idea, more likely a waste of time 😁😇. But the idea is to:
* 1.) Fetch latest D9 curated.json
* 2.) Fetch latest D10 curated.json
* 3.) Find missing recommendations in D10
* 4.) Check drupal.org if new release
* 5.) Update constraint if there is a new one, remove patches, mark as vetted:false
* 6.) If no new version, just add former recommendation
As we have seen in the Bean issue...even if a recommendation is unchanged it does not guarantee function on D10. So not entirely sure how to account for that.
n/a
run port-curated-d9.php script to update recommendations
TINKER 👷♂️
n/a
n/a
n/a
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
dan612 commentedComment #4
jienckebd commentedGreat idea and great work Dan.
If we land #3426231 to port the AMA install process to Drupal from ACLI and support installs with composer lenient or non-vetted recommendations, I'd like to MR a set of changes to curated.json with the remaining ~700 D9 curated recommendations (except for 16 that we're manually vetting in other issues) that can be installed as non-vetted in D10. We can look at refactoring the vetting process later, but the outcome of that experimental process could be committed as non-vetted without major impact. We could elevate recommendations to vetted once they're validated on real migrations.