Update the composer file to include the Drupal 10 compatible modules

the_g_bomb → closed merge request !11

I struggled rebasing the recent changes to the 2.x branch into the branch I had created initially, too many changes etc. So, I ended up closing the original MR and opening a new one.

I have nearly all the modules from the D7 version in this branch with the exception of 6 which aren’t available to D8/9/10 yet, and a further 7 which are no longer needed. They are outlined in the issue about splitting guardr_core: 📌 Split Guardr into Guardr Core, Guardr Audit, Guardr Extras Needs review

I am now struggling to get guardr_core D10 installed on a project,

I suspect that the lenient allow list doesn't cascade down through the composer dependencies.

I may have to add the various patch forks to get the D10 versions of the modules that don't have a valid release available yet.

MR 14 can be tested using:

composer create-project --no-interaction --no-install drupal/recommended-project:^10.0 guardrd10test
cd guardrd10test
composer config repositories.guardr_core vcs git@git.drupal.org:issue/guardr_core-3350324.git
composer require -W drupal/guardr_core:dev-3350324-update-to-D10-minimal

Still hoping these get merged:
email_confirmer - ✨ Drupal 10 compatibility Fixed
hacked - 📌 Upgrade code to Drupal 10 Fixed
logging_alerts - 🐛 User deprecated function: Theme functions are deprecated in drupal:8.0.0 and are removed from drupal:10.0.0. Use Twig templates instead of theme_emaillog_admin_settings() RTBC
paranoia - 📌 Automated Drupal 10 compatibility fixes Fixed
role_watchdog - 📌 Automated Drupal 10 compatibility fixes Fixed
state_log - 📌 Automated Drupal 10 compatibility fixes Fixed
view_profiles_perms - 📌 Automated Drupal 10 compatibility fixes Fixed

Hi Gareth, thank you for the issue and work!

I created a more minimal MR that didn't add any packages from the Guardr profile.

@Shrop and @Gareth does https://git.drupalcode.org/project/guardr_core/-/merge_requests/15 suffice for Drupal 10?

Thanks Joe and Gareth!

I like this and noting we did remove Hacked in this discussion. I think once we have the D10 version released, we can look at the other items around splitting things up more and some other upcoming changes.

I am also thinking we should do Drupal core reqs like this - ^9.3 || ^10 vs. ^9 || ^10 could protect us from dependencies requiring 9.3. We have some now.

Thank to the team here! Great to get this going and talk next steps.

Guardr Core 2.1.0 → released.

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