solo 1.0.37

Region link and border colours work again, and Solo no longer depends on solo.theme on Drupal 11.3+ (no Drupal 12 deprecation). Covers everything since 1.0.36, the last published release.

Requirements

• Drupal ^10.1 || ^11 || ^12.

Fixes

• Region link colours were ignored since 1.0.35 (#3629228: https://www.drupal.org/project/solo/issues/3629228). The link rule was wrapped in :where(), so solo-normalize.css won and links fell back to the text colour. Region link colours now apply again, while a paragraph's own link rules still take precedence.
• Region border colour lost to the colour scheme (#3629228). Schemes set the border variable on elements inside the containers and on form fields, buttons and menu items; those rules now skip content inside a region that sets its own border colour. Hover, focus and active states keep the scheme's border so they stay visible.
• Drupal 12 deprecation "Using solo.theme is deprecated". Solo now works fully without solo.theme on Drupal 11.3 and later: include files are loaded through a new SoloIncludes class, the three menu suggestion preprocess functions have #[Hook] methods, and the settings and search forms register their include files so a cached form still finds its callbacks. The file stays for Drupal 10 and is marked with core's #[ExtensionFileIsConverted].

Documentation

• Sub-theme README (#3629132: https://www.drupal.org/project/solo/issues/3629132): lists every file and every occurrence of solo_subtheme to rename, including the PHP namespace in src/Hook. A copy that keeps the old namespace fails with "Cannot redeclare class".
• The starter sub-theme's .theme file carries the same marker and says to put new code in src/Hook.

Tests

• New: RegionLinkColourRuleTest</coriableOverrideTest and
  ThemeFileIndependenceTest;

  Hode> now covers the suggestion preprocess
  functions.</li></ul>
  <h3>After updating</h3>
  <p>Run <code>drush updb

  , then drushods and a new class must be registered). This
release adds no database updates.