[hostellerie]

Summary

Monitor 1.5.0 builds on the 1.4.0 modernization work with reliability improvements, clearer configuration help, improved plugin discovery and safer release packaging.

The plugin remains focused on site health, diagnostics, operational monitoring and actionable recommendations, with a read-only-first approach.

Main changes

• Fix plugin reactivation when Monitor is loaded from Geeklog plugin-management contexts where the database table prefix is not otherwise imported.
• Add native Geeklog Configuration tooltips for Monitor settings.
• Add an idempotent same-version 1.5.0 configuration repair path for early 1.5.0 installations.
• Preserve existing administrator configuration values during metadata repair.
• Improve GitHub release/tag cache behaviour:
  • 4-hour cache for anonymous API access;
  • 1-hour cache when a GitHub token is configured;
  • manual refresh continues to bypass the cache.
• Sort Discover plugins alphabetically.
• Improve plugin catalog compatibility and release metadata handling.
• Keep Monitor diagnostics read-only-first and provider-aware.
• Clarify that marketing mapping, content clusters and editorial relationships belong to the Hub plugin rather than Monitor.
• Prepare future diagnostics for:
  • missing, short, long or duplicate SEO metadata;
  • incomplete language packages;
  • orphaned plugin database registrations.

Compatibility

Target compatibility remains:

• Geeklog 2.1.1 through 2.2.2
• PHP 5.6 through 8.1

The implementation continues to use the common compatible subset required by these environments.

Distribution and CI

• Remove the obsolete dist/monitor_1.4.0_2.1.1.zip.
• Add the current dist/monitor_1.5.0_2.1.1.zip.
• Improve the distribution workflow so archive publication tolerates concurrent branch updates without overwriting newer source.
• Latest archive build workflow passes successfully.

Documentation

Updated:

• README.md
• ROADMAP.md
• RELEASE-NOTES-1.5.0.md
• docs/UPGRADE-1.5.0.md
• configuration audit documentation
• Geeklog API compatibility documentation
• services/capability documentation

Upgrade notes

No destructive migration is introduced by Monitor 1.5.0.

Existing 1.4.0 migration and compatibility-repair logic remains available for older installations.

Early installations already reporting pi_version = 1.5.0 can repair final configuration metadata without requiring an artificial 1.5.1 version bump.

Scope

Monitor remains responsible for diagnostics and operational visibility.

Content relationships, pillar/cluster ownership and marketing/editorial mapping remain the responsibility of Hub. Monitor may diagnose missing capabilities or unlinked content but does not duplicate Hub's relationship graph.

Release package

The repository now contains the current installable archive:

dist/monitor_1.5.0_2.1.1.zip