Lock GitLab CI to max supported version

Created on 5 August 2025, 3 days ago

Problem/Motivation

Tests have been failing due to gitlab_templates updating to 11.2. This is expected behavior from templates and aligns with how s3fs has selected versions to test.

s3fs however being on a "per minor" release cycle already has to make a commit to increase the supported version of Drupal, it would be a minor effort to increase the version either at the time we add next minor/major support, or shortly after a Core release is made.

The advantage of this would be that s3fs would not fail when next minor is release, and can adjust the timeline based on our readiness with less disruption to pipelines.

Steps to reproduce

Review existing failing pipelines for past month.

Proposed resolution

Hard code Core target version to currently supported maximum minor.

Remaining tasks

User interface changes

None

API changes

None

Data model changes

None

πŸ“Œ Task
Status

Active

Version

3.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States cmlara

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024