Modify Migrate Plus version constraint after 6.x bugfix release

Created on 19 July 2024, 5 months ago
Updated 20 July 2024, 5 months ago

Problem/Motivation

In πŸ“Œ Set up conflict with Migrate Plus 6.0.3+ Active , we had to mark Migrate Plus 6.0.3+ as a non-applicable test dependency because its 6.0.3 patch release was shipped with a non-BC change in its source plugins. See πŸ› Fix backwards-incompatible Json data_parser API change included in 6.0.3. Needs work .

Proposed resolution

After a fix is released, modify our Migrate Plus version constraint to exclude broken versions (hopefully, only 6.0.3).

Remaining tasks

  1. In πŸ“Œ Set up conflict with Migrate Plus 6.0.3+ Active , the Migrate Plus version constraint was changed to >=5.0 <6.0.3
  2. In the ticket MR, change the Migrate Plus version constraint back to the original one (^5 || ^6), or to any equivalent (>=5.0 <7 etc).
  3. Revisit the MR every time Migrate Plus has a new release, and re-execute the MR test pipeline.
  4. Once it passes with a newer Migrate Plus version, replace the version constraint to a new one which excludes the broken versions.
πŸ“Œ Task
Status

Active

Version

2.0

Component

Code

Created by

πŸ‡­πŸ‡ΊHungary huzooka Hungary πŸ‡­πŸ‡ΊπŸ‡ͺπŸ‡Ί

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