PHP digest — 9 October 2026
PHP 8.5.12RC1 available for testing
The release managers announced PHP 8.5.12RC1 at
00:59 UTC on 9 October (git tag php-8.5.12RC1). PHP 8.5.12 is expected on 22 October 2026. The
same date is planned for 8.4.27, whose RC1 was announced
on 8 October. Release candidates are for testing, not production.
The 8.5.12RC1 NEWS (dated 8 October) is a long list of bug fixes. Many are crash, memory-safety and correctness fixes, in OPcache and the tracing JIT, PDO, DOM, Intl, the CLI built-in server and the bundled Lexbor library. Entries that change visible behavior include:
pg_service()is removed. NEWS describes it as "unavailable with any released libpq".PDO_DBLIBnow reports errors raised bybeginTransaction(),commit(),rollBack()andlastInsertId()instead of dropping them (GH-23741).grapheme_strstr()andgrapheme_strpos()now find canonically equivalent matches, andgrapheme_strstr()/grapheme_stristr()return correct substrings when supplementary characters come before the match.Dom\HTMLDocument::getElementById()now finds ids on SVG and MathML elements.- The OPcache optimizer no longer folds
$cond ? -0.0 : 0.0into a single-0.0(GH-24063).
Several entries mention heap buffer overflows or use-after-free bugs. They are not described here as vulnerabilities, because no security advisory for these releases was checked. The NEWS file was read through a fetch limited to about 18,000 characters, so the last entries of the RC section may be missing. The final 8.5.12 NEWS can differ from the RC.
ext/csv RFC opens for discussion
The CSV extension RFC, a draft on 8 October,
is now Under Discussion. Its author opened the internals thread
at 06:19 UTC on 9 October, and the official RFC index lists it as discussion. At that point the proposal was unchanged:
an always-enabled ext/csv with six Csv\ functions and a lazy Csv\LazyLaxCollection, RFC 4180 defaults,
no escape character, proposed for the release after PHP 8.6. The author asked for feedback on the API, the
LazyLaxCollection name and whether the extension should be optional at build time. In reply to the first
question, the author said they are considering
Csv\collection_to_stream() and LazyLaxCollection::createFromStream() for already-open streams. These are not in
the RFC yet. At 19:43 UTC the author published version 1.1,
revised after a review of the implementation. Parsing is now strict for every dialect: whitespace before an
opening enclosure, data after a closing enclosure, an unclosed enclosure and a bare CR or LF outside an enclosed
field throw ValueError. An LF-only file therefore needs eolSequence: "\n". File-backed collections own their
stream like SplFileObject. The stream entry points are still absent. No vote is scheduled. See the RFC page.
Symfony 8.2: single-use signed URLs, expiration required in 9.0
A Symfony blog post describes
three 8.2 changes. UriSigner's sign(), check(), checkRequest() and verify() take a new $version
argument that is included in the signature but not in the URL. A link stops working when that value changes,
for example a password hash after a reset (#64408). Calling UriSigner::sign() without an expiration is
deprecated and will be required in Symfony 9.0. A default can be set with the $defaultExpiration
constructor argument or the framework's uri_signer.expiration option (#64455). createLoginLink() accepts
signed $parameters, which are exposed in the _login_link_parameters request attribute (#64271). The post
warns to read those values from the attribute, not the query string. It is filed under "Living on the edge".
Vote on exceptions for invalid number-base input announced for 16 October
The author of the number base functions RFC
announced at 10:41 UTC that the vote opens on Friday 16 October.
The RFC (version 0.3, Under discussion, PHP 8.7, 2/3 majority) would make bindec(), octdec(), hexdec()
and base_convert() throw instead of silently ignoring invalid characters, which they have done with an
E_DEPRECATED notice since PHP 7.4 (hexdec('z') returns 0 today). Version 0.3 throws a plain Exception,
not the ValueError still named in the index and thread titles. Code that passes separators, such as
hexdec('1234-5678'), would break. An earlier vote announcement was not followed by a vote, so this is a
plan, not an opened ballot. See the RFC page.
Coverage
All 43 sources were collected successfully at 04:01 UTC, and the 24 due feed and index sources again
at 10:01 UTC (the daily package and adoption sources were not due). health --fail-stale reports no
failed or stale source. The 04:01 run added PHP 8.5.12RC1, PHPStan 2.3.1 package metadata (already covered on
8 October) and a "This Week In PHP Internals" video post (message 132842). That
post is a secondary summary and has no item. The 10:01 run added the ext/csv discussion thread (messages
132843, 132845, 132848), list replies on the Filter enums RFC (a
type-safety objection to combining flags through backing values; the vote question was filled in) and the
Time\Instant RFC (naming and coarse-clock review comments), which are
recorded on the RFC pages and have no item here, and the Symfony post. The official RFC index now has 950
entries (csv_extension added as discussion; end_pear_endorsement and reldateformatter are voting).
The 16:02 UTC run collected the 24 due sources without failures. It added the number-base vote announcement
above, a 14-point review of the Uri\QueryParams RFC, the voting widget added to
the Io\Terminal RFC (API unchanged, no vote date) and further replies on the
bcrypt-sha256, Filter enums and Time\Instant RFCs. These are recorded on the RFC
pages and have no item here. It also added a Laravel News article and a freek.dev post (secondary, not used).
The RFC index still has 950 entries with no status changes.
The 22:01 UTC run again collected the 24 due sources without failures. It added ext/csv version 1.1 (above),
a further bcrypt-sha256 reply recorded on that RFC page, and Doctrine ORM 3.7.5, a three-PR bugfix release
with no item. The RFC index still has 950 entries with no status changes. Package and WordPress version-share observations
were not compared, because no baseline comparison has been defined.