Deprecate delighted package - Delighted sunset June 30, 2026

[jflores-q]

Summary

Delighted is being sunset on June 30, 2026. This is the final release of the delighted/delighted PHP package (v4.2.0), marking it as deprecated.

For more information, visit the Delighted Sunset FAQ.

Changes

• lib/Delighted/Version.php: Bumped version to 4.2.0. Added @trigger_error() with E_USER_DEPRECATED to issue a runtime deprecation notice when the package is loaded.
• composer.json: Updated author_email for Ben Turner from ben@delighted.com to hello@delighted.com (the active support address).
• README.md: Added deprecation banner at the top (visible on Packagist).
• CHANGELOG.md: Added 4.2.0 deprecation entry.

What users will see

On composer install/composer update: Packagist "abandoned" warning (once applied via Packagist web UI).

At runtime (when the Client class is used): An E_USER_DEPRECATED notice is triggered, which appears in error logs and deprecation-aware tools (Symfony deprecation logger, PHPStan, etc.).

On the Packagist page: "This package is abandoned" banner + deprecation banner in README.

Pre-merge validation (all passed)

Check	Result
php -r "require 'lib/Delighted/Version.php'; echo \Delighted\VERSION;"	Outputs 4.2.0
E_USER_DEPRECATED fires	Caught by error handler, message correct

After merging

1. Tag the release as v4.2.0
2. Push the tag (Packagist auto-syncs from tags)
3. Mark as "Abandoned" on Packagist
4. Archive this GitHub repository

Local validation steps

1. Verify version constant

php -d error_reporting=E_ALL -r "require 'lib/Delighted/Version.php'; echo \Delighted\VERSION . PHP_EOL;"
# Expected: 4.2.0

2. Verify E_USER_DEPRECATED fires

php -d error_reporting=E_ALL -r "
set_error_handler(function(\$errno, \$errstr) { echo 'CAUGHT: ' . \$errstr . PHP_EOL; });
require 'lib/Delighted/Version.php';
echo 'Version: ' . \Delighted\VERSION . PHP_EOL;
"
# Expected: "CAUGHT: The delighted/delighted package is deprecated..."