Breaking Rules Dependency for < 10.3

Created on 1 July 2024, 2 months ago
Updated 15 July 2024, about 2 months ago

Problem/Motivation

A recent commit updated the rules requirement to 4.0, which requires >= Drupal 10.3. This causes dependency errors for sites not ready to upgrade to ^10.3.

Steps to reproduce

On a site running < Drupal 10.3, attempt to install Rules Essentials with the current Rules 4.0 requirement.

Proposed resolution

Create new branches/releases for ^10.3 || ^11 and ^9.3 || ^10 separately so developers can follow the upgrade path.

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Fixed

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States tommasorandazzo

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

Merge Requests

Comments & Activities

  • Issue created by @tommasorandazzo
  • Open on Drupal.org β†’
    Core: 9.5.5 + Environment: PHP 7.3 & MySQL 5.7
    last update 2 months ago
    Waiting for branch to pass
  • Pipeline finished with Failed
    2 months ago
    Total: 189s
    #213136
  • Issue was unassigned.
  • Status changed to Needs work 2 months ago
  • πŸ‡ΊπŸ‡ΈUnited States tommasorandazzo

    Marked the MR as a draft as this is not a solution. Collaboration with the maintainers is needed to separate the change between releases, however this MR allows a temporary workaround without targeting a specific commit hash.

  • πŸ‡ΊπŸ‡ΈUnited States TR Cascadia

    Yeah I meant to do that in a new branch. This module is going to be unstable for the next week as I sort out all the changes required by Rules and TypedData to support 10.3 and 11.

  • Status changed to Fixed 2 months ago
  • πŸ‡ΊπŸ‡ΈUnited States TR Cascadia

    I reverted the change to composer.json in the 8.x-1.x branch, and opened a new 2.0.x branch for D10.3 support.

    Note that because of breaking changes in core 10.3, you will have to move to 2.0.x when you eventually upgrade to 10.3. I will be marking 8.x-1.x as unsupported soon.

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

Production build 0.71.5 2024