Problem/Motivation

The latest release notes read:

Once you upgrade to Drupal 10.2 and none of your code still refers to the Drupal/variationcache namespace, it is safe and recommended to turn off and remove this module.

However, the vast majority of VC users installed it as a dependency for Group and Flexible Permissions, yet there's no release (anytime soon) of either of those that can stop using VC. So these release notes are a bit misleading.

Steps to reproduce

Proposed resolution

Update both the latest release notes and the project page, to say something like:

This module is still a dependency of flexible_permissions and therefore, group. It will require a new major version (v4) of Group to make the required changes to only use Core APIs, and there is no planned date for such a release. Until then using the latest release of VariaitionCache is safe and expected.

Remaining tasks

  1. Refine the blurb
  2. Update the project page
  3. Update the 8.x-1.5 release notes

User interface changes

API changes

Data model changes

Comments

dww created an issue.

monaw’s picture

monaw commented

i am currently caught in this problem...i am using the latest Group (3.2.2) and Flexible Permission (tried 1.0 and 1.1.0) and have not been able to upgrade to D10.2.* due to variationcache errors (see https://www.drupal.org/project/variationcache/issues/3441917#comment-156...).

would really appreciate some help with this...i'm currently stuck

monaw’s picture

monaw commented

ok, i finally resolved my problem and was able to upgrade to D10.2.6; see https://www.drupal.org/project/variationcache/issues/3441917#comment-156... (hope that may help someone else)

mortona2k’s picture

mortona2k commented

Variationcache is no longer a dependency of Flexible Permissions as of 2.x.

https://git.drupalcode.org/project/flexible_permissions/-/commit/b223cf3...

However, group still depends on variationcache with require-dev.

https://git.drupalcode.org/project/group/-/blob/3.3.x/composer.json?ref_...