selectify 2.0.6

Updating from an earlier release no longer takes the site down until caches are rebuilt; a CSS fix for Selectify's own widget styles. Covers everything since 2.0.5, the last published release.

Requirements

• Drupal ^10 || ^11 || ^12, PHP 8.1+.
• The selectify_webform sub-module needs Webform. Webform has no Drupal 12 release yet: on Drupal 12 it fails to load (WebformHandlerManager::getGroupedDefinitions() is incompatible with core), so selectify_webform cannot be used there until Webform supports Drupal 12. Selectify itself is not affected.

Fixes

• HTTP 500 on every page after an update, until drush cr (#3628961: https://www.drupal.org/node/3628961). The #[LegacyHook] wrappers fetched the hook classes with \Drupal::service(); those services were added in 2.0.5, so a site updated from an earlier release did not have them yet. The wrappers now use \Drupal::classResolver(), and the three hook classes build themselves from the container (ContainerInjectionInterface) with services that exist from 2.0.2 onwards.
• Styles wiped by all: unset. In rules where all: unset came after other declarations, it erased them (size, border, radius, background). It now comes first.

Tests and CI

• A Unit guard checks the wrappers and
  

   test runs the wrappers against a container
  without the hook services.</li>
  <li>CI runs the Drupal 12 job again ("next majot 13).</li></ul>
  <h3>After updating</h3>
  <p>Run <code>drush updb

  , then drush cr. This release adds no database updates. Sites updating from 2.0.1 or older must run both, because the modulctify.helper in 2.0.2.