[Experimental] Create script to automate unchanged recommendations

Created on 1 March 2024, 10 months ago
Updated 7 March 2024, 10 months ago

Problem/Motivation

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.

Steps to reproduce

n/a

Proposed resolution

run port-curated-d9.php script to update recommendations

Remaining tasks

TINKER πŸ‘·β€β™‚οΈ

User interface changes

n/a

API changes

n/a

Data model changes

n/a

πŸ“Œ Task
Status

Active

Version

1.9

Component

Recommendations β€” Drupal 10

Created by

πŸ‡ΊπŸ‡ΈUnited States dan612 Portland, Maine

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @dan612
  • πŸ‡ΊπŸ‡ΈUnited States dan612 Portland, Maine
  • Pipeline finished with Success
    10 months ago
    Total: 382s
    #107534
  • Pipeline finished with Success
    10 months ago
    Total: 369s
    #107535
  • πŸ‡ΊπŸ‡ΈUnited States jienckebd

    Great idea and great work Dan. You're awesome and I object to the current context.

    If we land #3426231 ✨ Port AMA install process from ACLI to Drupal Active 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 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.

Production build 0.71.5 2024