Problem/Motivation

Part of

As of v1.6.12 support for PHP 8.4 added and drop of 5.x

Proposed resolution

upgrade and backport to 10.4.x at least as no functional changes

Remaining tasks

review, commit

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Issue fork drupal-3471080

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

andypost created an issue. See original summary.

andypost’s picture

Title: Upgrade bovigo/vfsStream to v1.6.12 » Update mikey179/vfsstream to v1.6.12 for PHP 8.4

andypost’s picture

Status: Active » Needs review

It looks safe even for 10.3.x

andypost’s picture

Filed another MR to run tests using 10.4

smustgrave’s picture

Status: Needs review » Reviewed & tested by the community

Seems like a minor update from the release notes and didn't break anything.

Don't see any issue.

  • catch committed f9d89149 on 11.x
    Issue #3471080 by andypost: Update mikey179/vfsstream to v1.6.12 for PHP...
catch’s picture

Version: 11.x-dev » 10.4.x-dev
Status: Reviewed & tested by the community » Patch (to be ported)

Committed/pushed to 11.x, thanks!

Moving to 10.4.x for backport.

andypost’s picture

Status: Patch (to be ported) » Needs review

There's MR 9379 against 10.4.x branch already and not sure about 11.0.x

smustgrave’s picture

Status: Needs review » Reviewed & tested by the community

Assuming not 11.0 since that's already released.

  • longwave committed 8cfb163e on 10.4.x
    Issue #3471080 by andypost: Update mikey179/vfsstream to v1.6.12 for PHP...
longwave’s picture

Status: Reviewed & tested by the community » Fixed

Committed 8cfb163 and pushed to 10.4.x. Thanks!

While it's only a dev dependency so it technically could be backported, I don't think it's worth changing in 11.0.x now.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.