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

Issue fork tr_rulez-3458340

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

tommasorandazzo created an issue. See original summary.

tommasorandazzo opened merge request !5

tommasorandazzo’s picture

tommasorandazzo
they/them
CreditAttribution: tommasorandazzo at Third and Grove commented
Assigned: tommasorandazzo » Unassigned
Status: Active » Needs work

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.

tr’s picture

tr CreditAttribution: tr commented

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.

tr’s picture

tr CreditAttribution: tr commented
Status: Needs work » Fixed

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.

Status: Fixed » Closed (fixed)

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