Problem/Motivation

The path_file.info.yml declares
core_version_requirement: ^8.8 || ^9 || ^10 || ^11, so the
module cannot be installed on Drupal 12. Site owners on the D11→D12
upgrade path are blocked.

Proposed resolution

  • Add ^12 to core_version_requirement in path_file.info.yml.
  • Run Upgrade Status against Drupal 12 and fix any deprecations it reports.
  • Confirm the GitLab CI pipeline passes on the D12 job.

Remaining tasks

  • Bump core_version_requirement.
  • Resolve deprecations flagged by Upgrade Status / drupal-check.
  • Green CI pipeline on the D12 job.
  • Review + merge on the 2.2.x branch.
  • Tag a release.

User interface changes

None.

API changes

None expected.

Data model changes

None.

Issue fork path_file-3619691

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:

About issue forks

Comments

batigolix created an issue. See original summary.

batigolix opened merge request !21

batigolix’s picture

batigolix
Primary language Dutch
Location Utrecht
commented
Status: Active » Needs review
arjenk’s picture

arjenk commented
Status: Needs review » Reviewed & tested by the community

Tested with Drupal 11.4, php 8.4 and upgrade status module.

The 'upgrade status' module only gives 3 pre-existing remarks on 'Unsafe usage of new static()', no blocker. All tests are green. Before committing i would suggest that you uncomment the 

OPT_IN_TEST_NEXT_MAJOR: '1'

in .gitlab-ci.yml so Drupal 12 is added in the tests

batigolix’s picture

batigolix
Primary language Dutch
Location Utrecht
commented
Status: Reviewed & tested by the community » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

  • batigolix committed 9604c313 on 2.2.x 
    feat: #3619691 Drupal 12 support

By: batigolix
By: arjenk

Status: Fixed » Closed (fixed)

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