Problem/Motivation

As per https://www.hojtsy.hu/blog/2024-jul-05/continuous-forward-compatibility-... by enabling this future contributors would get feedback on whether their added code is compatible with the next major version of Drupal core.

Steps to reproduce

N/A

Proposed resolution

  1. Enable the flag it in gitlab-ci
  2. Resolve any new found issues

Remaining tasks

Create MR and see what gets revealed

User interface changes

N/A

API changes

N/A

Data model changes

N/A

Issue fork viewsreference-3459735

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

scott_euser created an issue. See original summary.

scott_euser opened merge request !63

  • scott_euser committed 4b8d981b on 8.x-2.x 
    Issue #3459735: Improve testing against future known deprecations
scott_euser’s picture

scott_euser commented
Status: Active » Fixed

Sorry this ended up being so trivial. I guess having thoroughly tested and added automated tests via a Drupal 11 default install paid off here. Should at least help for eventual Drupal 12.

Status: Fixed » Closed (fixed)

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