Problem/Motivation

Schema.org Blueprints already declares Drupal 11 compatibility in composer.json and schemadotorg.info.yml, but the GitLab CI configuration currently only runs the primary composer job against Drupal 10.5.x-dev.

To keep the 1.0.x branch covered against both supported major versions, CI should continue checking Drupal 10.x and also opt into Drupal 11.x testing, including Drupal 11.4.x.

Proposed resolution

Update .gitlab-ci.yml to keep the primary Drupal 10.x composer target and enable OPT_IN_TEST_NEXT_MAJOR so the DrupalCI template also tests Drupal 11.x.

Remaining tasks

  • Create an issue fork/branch.
  • Update .gitlab-ci.yml.
  • Confirm the CI configuration validates locally.
  • Run the GitLab pipeline/MR against Drupal 10.x and Drupal 11.x.

User interface changes

None.

API changes

None.

Data model changes

None.

AI-assisted by Codex.

Issue fork schemadotorg-3610733

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

jrockowitz created an issue. See original summary.

jrockowitz’s picture

jrockowitz commented
Issue summary: View changes

Updated the issue summary to clarify that CI should cover both Drupal 10.x and Drupal 11.x.

jrockowitz opened merge request !309

jrockowitz’s picture

jrockowitz commented
Status: Active » Needs review

Opened merge request: !309.

jrockowitz’s picture

jrockowitz commented
Status: Needs review » 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.

Status: Fixed » Closed (fixed)

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