- Issue created by @nicholosophy
- πΊπΈUnited States markusa
I think its possible that something else is causing a downgrade. CiviCRM Entity itself is not making any version requirements for CiviCRM
https://github.com/eileenmcnaughton/civicrm_entity/blob/4.0.x/composer.json{ "name": "drupal/civicrm_entity", "type": "drupal-module", "description": "Expose CiviCRM entities as Drupal entities.", "homepage": "http://drupal.org/project/civicrm_entity", "license": "GPL-2.0+", "require": { "drupal/core": "^10", "civicrm/civicrm-drupal-8": "*" }, "require-dev": { "drupal/fullcalendar_view": "^5.0" }, "minimum-stability": "dev" }
I'll look into it, but can't think of why it would downgrade from 5.67.3 to 5.67.1
- Status changed to Postponed: needs info
about 1 year ago 4:39pm 6 December 2023 - πΊπΈUnited States markusa
I tested upgrading a site from 5.63 to 5.67.3 and then upgrading CiviCRM, and also requiring into a blank D10 site
composer create-project drupal/recommended-project new-blank-d10
composer require civicrm/civicrm-core civicrm/civicrm-packages civicrm/civicrm-drupal-8
as of this date, 5.67.3 pulled in for CiviCRM, then
composer require 'drupal/civicrm_entity:^4.0@beta'Composer kept civicrm at 5.67.3 afterwards.
I'll need more specific information to assist
- π¦πΊAustralia nicholosophy Brisbane
Yeah this appears to be an incorrect report. Thanks for looking into this.
- Status changed to Closed: cannot reproduce
about 1 year ago 2:04am 7 December 2023