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

Issue fork s3fs-3539705

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

cmlara created an issue. See original summary.

cmlara credited taran2l.

cmlara’s picture

  • cmlara committed 9e2cae4b on 8.x-3.x
    Issue #3539705 by cmlara: Lock GitLab CI to max supported version
    
cmlara’s picture

Status: Active » Fixed

@taran2l apologies for the tag and extra emails this would of generated. I had multiple tabs open and credited you on the incorrect one.

Committed to Dev.

Status: Fixed » Closed (fixed)

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