Contrib.social

Caution in updating ECA

Open on Drupal.org →
Created on 22 June 2024, 6 days ago

Problem/Motivation

I am treading carefully WRT updating ECA to 2.00 and before I do, I wanted to be sure that the 1.x offering works perfectly with Drupal 10.3

To that end, I have updated ECA to 1.17 but I have two queries as a result of doing that...

Firstly, even though (locally) the contents of the modeller_bpmn\eca_modeller_bpmn.info.yml clearly read...

name: 'ECA BPMN'
type: module
description: 'Common functionality for all BPMN based modeller implementations.'
core_version_requirement: ^9 || ^10
package: ECA
dependencies:
  - eca:eca_ui

# Information added by Drupal.org packaging script on 2024-06-21
version: '1.1.7'
project: 'eca'
datestamp: 1718958109

When a I run a composer update --dry-run, in addition to the expected Drupal core...

  - Upgrading drupal/core-composer-scaffold (10.2.7 => 10.3.0)
  - Upgrading drupal/core-project-message (10.2.7 => 10.3.0)
  - Upgrading drupal/core (10.2.7 => 10.3.0)

I am also seeing that there is a proposal to update...

Upgrading drupal/eca_modeller_bpmn (1.1.6 => 1.1.7)

Which can't be right given that (as above) the eca_modeller_bpmn.info.yml is already 1.17.
What might going on there I wondered?

Secondly, I am seeing a proposal to update drupal/eca_ui (1.1.6 => 2.0.0) which I really don't want to do just yet as I want to stay solely on the 1.1x codebase until I am certain that 2.x works with all my models.

Is it safe to update drupal/eca_ui (1.1.6 => 2.0.0) even though everything else is still using 1.1.x?

I might be being over-cautious here but I don't want to run into any breakages.

Many thanks

💬 Support request
Status

Active

Version

1.1

Component

Miscellaneous

Created by

🇬🇧United Kingdom SirClickALot Somerset

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

Comments & Activities

  • Issue created by @SirClickALot
  • Comment 6 days ago →
    🇩🇪Germany jurgenhaas Gottmadingen

    Updating to Drupal 10.3 first while still remaining on ECA 1 is the recommended approach because Drupal 10.3 comes with some significant changes in itself, so getting that up and running first is great. Only then should you start updating other components like e.g. ECA (and related modules) from 1 to 2.

    What you're seeing about eca_ui and other (in fact all about eca_*) is an oddity of the Drupal composer facade. There is only really the drupal/eca package in either version 1 or 2. All the sub-modules in that package are exposed to the outside world as well, but that's misleading. You can't actually install e.g. eca_ui in a different version from the main eca package.

    When it comes to the independent package bpmn_io, that is also available in version 1 or 2. If your constraints in composer.json allow both, then it checks for bpmn_io 2.0.0 and that requires eca 2.0 as well. That's why you see that suggestion you mentioned above.

    In order to only update Drupal core to 10.3 and leave ECA et al at version 1, make sure that you have the following constraints in your composer.json:

        "drupal/core": "^10.3",
    "drupal/bpmn_io": "^1",
    "drupal/eca": "^1",

    That will remain on ECA 1 for all its components and updates core to 10.3.

  • Comment 6 days ago →
    🇬🇧United Kingdom SirClickALot Somerset

    Thank you for the clarification.

    I have now updated to Drupal 10.3 and, WRT the ECA and BPMN.io, my current composer.json reads...

    ...
"drupal/bpmn_io": "^1.1",
"drupal/eca": "^1.1",
...

    Is that still OK for sticking (since you mention "^1 above)

  • Comment 6 days ago →
    🇩🇪Germany jurgenhaas Gottmadingen

    Yes, you can see the constraint documentation at https://getcomposer.org/doc/articles/versions.md#writing-version-constra...

    A constraint ^1.1 means at least version 1.1.1 and lower than 2.0.0

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024