2.5.7

What's Changed

• Another Drupal 11 Fix by @ragnarkurmwunder in #44

Full Changelog: 2.5.6...2.5.7

Namespace Fix

• Fix use namespaces
• Fix tests
• Add type hints

Fix namespace resolution and ensure Drupal 11 compatibility

(QAG-69): Improve README.md structure and content
(QAG-69): Update README with Drupal 11 compatibility and improved troubleshooting
(QAG-69): Add GPL-2.0-or-later license to composer.json
(QAG-69): Update version to 2.5.5 in composer.json

Credits: @tormi

Version control

Added tighter version control to prevent version mismatch mishaps -- composer.json vs release.

2.5.3

What's Changed

• Version: Bump by @ragnarkurmwunder in #39

Full Changelog: 2.5.2...2.5.3

Bug fix: Namespace problem

What's Changed

• Fixed a bug that, under certain conditions, failed to find \update_cron(), leading to a crash in cron execution.

Drupal 11 compatibility

D11 compatibility

Log current modules too

We have kept back logging up-to-date modules because of the risk that log entries are getting too big, and might not be digested by logging systems.
However, we need this data.
Not all sites have massive amounts of modules.
The expected limit for logging systems is 64k. A hefty statistical log entry is expected to be 10k.

Refresh refactor

The module data refreshing has been refactored again.
It is a real challenge to get it unstable.

Packaging refactoring

• Packaging (composer.json and updates_log.info.yml) has been refactored.
• Packaging is now according to custom packaging
• Refactored self-version lookup