Release v3.3.0 · renatobo/eventon-apify

New Features

Raised the minimum supported WordPress version to 7.0. The plugin header, readme.txt, the PHPCS minimum_supported_wp_version used by the deprecation sniffs, and the README badge now all state the same floor, so a deprecated-API warning fires against the version the plugin actually claims to run on. WordPress enforces the header at activation, so sites below 7.0 cannot activate this build.
Dropped the PHP 7 fallback path. Plugin::boot() no longer branches on version_compare(PHP_VERSION, '8.0.0', '<') to load a bare bootstrap and print an admin notice. Requires PHP: 8.0 in the plugin header is the enforcement point, and WordPress refuses activation below it, so the runtime branch could only ever run on a site where activation had already been blocked. The now-unused eventon_apify_php_version_notice() was removed with it.
Tightened the php-stubs/wordpress-stubs dev requirement to ^7.0. Static analysis now resolves core signatures against the same WordPress line the plugin supports, instead of allowing a 6.x stub set to satisfy the constraint.

This release changes supported-platform metadata only. No endpoint, payload, option, or capability behavior changes, and no migration is required for sites already on WordPress 7.0 and PHP 8.0.
The PHP floor itself is unchanged at 8.0. composer.json, the CI matrix (8.0, 8.3, 8.5), and the plugin header already required it; only the redundant runtime guard was removed.
EventON remains a hard runtime dependency, declared at runtime rather than through the Requires Plugins header, for the reasons recorded in the 3.2.3 notes.