Add core_version_requirement: ^8 || ^9 to blockgroup.info.yml to designate that the module is compatible with Drupal 9. See https://www.drupal.org/node/3070687.

CommentFileSizeAuthor
#2 3131738-2.patch289 bytesyogeshmpawar

Comments

yogeshmpawar created an issue. See original summary.

yogeshmpawar’s picture

yogeshmpawar
He/Him/His
Primary language English
Location Pune(MH), INDIA 🇮🇳
commented
Assigned: yogeshmpawar » Unassigned
Status: Active » Needs review
Issue tags: +Drupal 9 compatibility, +Drupal 9 readiness, +Drupal 9 porting day
StatusFileSize
new 3131738-2.patch289 bytes

Here's the patch for Drupal 9 readiness.

  • geek-merlin committed 2c5b9f4 on 8.x-1.x 
    Issue #3131738 by yogeshmpawar: Drupal 9 readiness
geek-merlin’s picture

geek-merlin
Primary language German
Location Freiburg, Germany
commented
Status: Needs review » Fixed

Thanks!

kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented
Title: Drupal 9 readiness » Drupal 9 compatibility
Issue tags: -Drupal 9 readiness

Per a Slack discussion with Gábor Hojtsy last year regarding usage of D9 tags (Drupal 9, Drupal 9 compatibility, Drupal 9 readiness, etc.), "Drupal 9 compatibility" should be used for contributed projects that need updating and "Drupal 9" was the old tag for D8 issues before the D9 branch was ready. Doing title and tag cleanup here based on that discussion. Please use "Drupal 9 compatibility" for titles and tags on other issues. Thanks.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.