Use Upgrade Status instead of drupal-check in stats/project_analysis

Created on 18 May 2020, almost 5 years ago
Updated 10 July 2023, over 1 year ago

Problem/Motivation

Use Upgrade status instead of drupal check to determine if modules are compatible with Drupal 9.

This will allow determining if a module is compatible with Drupal 9 and updating the info.yml files if it is.

Proposed resolution

Use upgrade status once before rector is run and once after. If the only problem after rector is run is the info.yml then update the info.yml file.

Drupal will have to installed but we can do it once and have the drupal clone checkouts use the sqlite file as a starting point.

Remaining tasks

  1. Determine if we should run upgrade status on all sub modules of a project and update their info files too.

User interface changes

API changes

Data model changes

Release notes snippet

๐Ÿ“Œ Task
Status

Fixed

Component

Code

Created by

๐Ÿ‡บ๐Ÿ‡ธUnited States tedbow Ithaca, NY, USA

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024