2.2.0 Release Plan

Changelog updated.

It was discussed that this is going to be a minor release over just a patch. Going to create a 2.x branch for future work.

With the release of Drupal 11 a few days ago, before we tag the 2.2.0 release, I'd like for us to get a fully clean GitlabCI test report. Currently, "phpunit (next major)" is failing. I don't think that there's a Drupal core 12.x branch yet (via https://git.drupalcode.org/project/drupal), so I'm not sure if we should just disable that test for now, or another option.

I'm guessing that maybe "phpunit (next major)" is running against the 11.x branch and am working to confirm this (https://drupal.slack.com/archives/CGKLP028K/p1722796036303819).

...a few minutes pass... Whoops, I just noticed 📌 Update fixtures for run updates Active - glad we're on the same page 😀

Before tagging a release, I'd like to get ✨ Smart Trim Tokens for text with summary fields Needs review merged as well.

-mike

Merged and closed #2782455. Just have the one blocker for this release.

#3464532 has been merged. No more blockers.

Final blockers are gone and Changelog updated.

Hope you can fix https://www.drupal.org/project/smart_trim/issues/3468760 🐛 Support D7 migrations Active as this is blocking D7 upgrades what becomes more an more time pressing.

@marc.bau Unfortunately the release happened before the issue was created. We will have to investigate.

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