Contents
When is core version required for test modules?
Prior to 8.8.2, the value is required for test modules and will cause site errors if it is not included. These errors are even encountered if $settings[‘extension_discovery_scan_tests’] = TRUE; is not enabled in settings.php.
Are there any portable modules for PowerShell Core?
Portable modules are modules that work in both Windows PowerShell and PowerShell Core. While .NET Framework and .NET Core are highly compatible, there are differences in the available APIs between the two.
How to make a module compatible with Drupal core?
The new core_version_requirement key in *. info. yml files for modules, themes, and profiles now supports semantic versioning as implemented by the Composer project. This allows modules, themes, and profiles to also specify that they are compatible with multiple major versions of Drupal core.
When to omit core version requirement in Drupal?
Note that test modules can omit the core_version_requirement key entirely as of Drupal 8.8.2, so that they will work with any core version they are tested against. Prior to 8.8.2, the value is required for test modules and will cause site errors if it is not included.
Where to find compatible modules in PowerShell 6.1?
For modules that come as part of Windows (or are installed as part of a role or feature), PowerShell 6.1 and above treat the CompatiblePSEditions field differently. Such modules are found in the Windows PowerShell system modules directory ( %windir%\\System\\WindowsPowerShell\\v1.0\\Modules ).
Why do I need core version in info.yml?
For example a module that is compatible with Drupal 8 and Drupal 9 can have a info.yml file like this This specifies that the module is compatible with all versions of Drupal 8 and 9. The core: is required here because Drupal Core versions before 8.7.7 do not recognize the core_version_requirement: key.