PHP digest — 6 October 2026
PHPStan 2.3.0: faster analysis, with generics and unused-variable checks in bleeding edge
PHPStan 2.3.0 was released at 06:33 UTC,
as the 2.2.17 notes had announced. The release post
reports that analysing WordPress core on the author's laptop took 60.5 s with 2.1.33 (December
2025) and takes 7.9 s with 2.3.0 and the optional PHPStan Turbo extension, which most installs
enable automatically (19.5 s without it). These are the maintainer's own benchmarks. The result
cache is no longer discarded on every Composer dependency or Symfony container change. Two
headline features are opt-in through bleedingEdge.neon: generic types inferred from how a
new Foo() object is used later, without generalizing scalars, and new unused-variable and
unused-assignment errors (variable.unused, assign.unused, assign.overwritten and others).
PHPStan still requires PHP ^7.4|^8.0. Evidence note.
Rector 2.7 adds four rules and requires PHPStan 2.3
Rector 2.7.0, released at 08:47 UTC, adds
TernaryToNullsafeCoalesceRector, BoolReturnTypeFromBooleanConstAndStrictReturnsRector,
ConstructorReadonlyAssignToDefaultRector and RemoveOverriddenAssignBeforeIfElseRector.
Its file cache is now keyed on project-relative paths, so it survives a change of checkout. The
notes report up to about 24% fewer CPU instructions for name imports on large projects, and fix
files being skipped silently when the only parallel worker is respawned. A Privatize*Rector fix
drops final when changing protected to private, because private final is forbidden on
PHP 8.4. The bundled Doctrine, Symfony and PHPUnit rule sets also changed. The tagged
composer.json
requires phpstan/phpstan ^2.3.0, so upgrading Rector also brings in PHPStan 2.3.
Symfony 8.2 orders listeners, tagged services and decorators by name
A Symfony blog post
describes new before and after options in the upcoming 8.2. With them an event listener,
subscriber or tagged service can name the services it must run before or after, for example
#[AsEventListener(before: LocaleListener::class.'::onKernelRequest')], instead of guessing a
priority number. Decorators get matching within and around options. Ordering is resolved when
the container is compiled. References to missing listeners are ignored, so optional bundles can
be named. Circular constraints, conflicting priorities and invalid methods are compile errors.
When a priority is also set, the constraints only reorder services within that priority.
WordPress 7.1.3 fixes seven security issues; older branches get backports
WordPress 7.1.3,
announced at 17:00 UTC, is a security and maintenance release with seven security fixes and four
bug fixes. The fixes cover a stored XSS on the Comments administration page through pending
comments, a DoS in WP_Http::make_absolute_url(), a second-order SQL injection in WXR export,
Author-role users being able to sticky posts, unauthenticated disclosure of comments on private
and unpublished posts, XSS through Imgur embeds, and forgeable parameters to the {status}_{type}
hook that can cause action name collisions. The project recommends updating immediately; sites
with automatic background updates are updated automatically. The announcement says backports
to branches back to 4.7 are "in progress". The releases archive
already lists 6 October releases from 7.0.7 and 6.9.10 down to 5.4.24. Only the latest 7.1
release is actively supported. The announcement gives no CVE IDs or severity ratings. The
version 7.1.3 page says
"one security fix" but lists the same seven issues.
RFC in discussion: one php binary that can also run FPM
The Single binary for CLI and FPM RFC
(version 0.1) entered discussion and was announced on internals
at 10:32 UTC. A proposed --enable-cli-fpm build option links the FPM SAPI into php, which then
runs FPM when its first argument is --fpm or when it is invoked as php-fpm* (for example a
symlink). The standalone php-fpm is still built. The author's Bref/AWS Lambda measurements show
an 18% smaller zipped runtime and a median FPM cold start of 211 ms instead of 280 ms. In a combined build,
PHP_BINARY in FPM mode points to php. Early replies raised that point, distribution packaging
and the conflicting -F flag. Later, Larry Garfield asked whether this privileges FPM over
other SAPIs such as FrankenPHP. Nicolas Grekas proposed
the reverse, an FPM binary that embeds the CLI, and Jakub Zelenka
agreed that this makes more sense. The RFC page
has not changed. A secondary vote would decide whether the option is on by default.
It is proposed for PHP 8.7, and no vote is scheduled. Evidence note.
Uri\QueryParams RFC reworked; author aims for a vote soon
The author of the query parameter RFC
posted a changelog at 13:37 UTC. The changes are
a readonly class, a QueryParamNullPolicy enum (SkipTuple, KeyOnly, EmptyString) for
null values, getQueryParams()/withQueryParams() on Uri\Rfc3986\Uri and Uri\WhatWg\Url,
and specified parsing edge cases. The author wants to bring it to a vote "as soon as possible (but
not sooner)", but no vote has been announced and the page still reads Under Discussion, proposed
for PHP 8.7. Evidence note.
Coverage
The 24 due feed and index sources were collected successfully at 10:01, 16:01 and 22:01 UTC.
The 19 daily package and adoption sources last succeeded at 04:01 UTC and were not due. health
reports no source stale. This edition has six developments, all from 6 October. The 16:01 update
added the single-binary RFC and the QueryParams rework. The 22:01 update added WordPress 7.1.3
and the replies proposing an inverted single-binary design. Other replies the same day did not get
items: the author of the invalid Filter options RFC on the superglobal filter defaults, and the
Time\Instant, Io\Terminal, PASSWORD_BCRYPT_SHA256 and b prefix threads, plus a pre-RFC
discussion of an ICU skeleton-based IntlNumberFormatter for unit formatting (GH-24165). A
Time\Instant page edit adding DateTimeInterface::toInstant() to its BC section also has no
item. None of these changed a status. In the official RFC index, single-binary-cli-fpm is new
(discussion), and end_pear_endorsement is still the only RFC in voting. The php.net release
record is unchanged. Package and WordPress version-share observations were not compared.