Five dated news digests and five engineering Q&A entries. Each item cites primary documentation or release artifacts (not generic placeholders).
The PHP project’s 8.4 announcement documents major language features including native property hooks, asymmetric property visibility, and lazy object initialization via reflection.
Frameworks like Symfony and Laravel publish their own adoption notes—read both.
Release managers published 8.4.1 quickly; internal change logs on php.net list CVE-class fixes that teams must deploy before public exposure.
Mirror only signed release artifacts.
The PHP Foundation blog contextualizes the number of RFCs merged and highlights DOM parser improvements aligned with HTML5 parsing rules.
Use it when briefing executives on upgrade cost.
Archive pages list dated announcements useful when proving due diligence during compliance reviews.
Link specific archive entries in change tickets.
Native extension maintainers should follow php-src UPGRADING files for each minor to catch zval and object handler signature changes.
Run phpize builds on CI for every supported platform.
Property hooks change how accessors run; validate Doctrine and Eloquent behaviors on hot entities before enabling hooks widely.
Add benchmarks for hydration-heavy endpoints.
Maintainers documented that 8.4.0 tags were not distributed; deploy 8.4.1+ per official announcements.
Update Docker base images accordingly.
The PHP Foundation roundup summarizes DOM improvements; cross-check with your HTML sanitizer pipeline and regression tests for malformed markup.
Capture before/after DOM trees in tests.
Follow distribution security notices in addition to php.net—they may lag upstream but include libc interactions.
Automate version probes in health checks.
Enable PHPStan/Psalm bleeding rules after upgrading; asymmetric visibility can surface latent encapsulation violations in legacy codebases.
Run analysis on CI with the same PHP minor as production.