Problem/Motivation

The FieldPurger service compatibility boundary introduced in Drupal 11.4 is repeated as a hard-coded version string in several Cloud code paths.

Proposed resolution

Add CloudServiceInterface::FIELD_PURGER_SERVICE_INTRODUCED_VERSION and use it for the FieldPurger compatibility calls in the shared module test base and uninstall validators.

Remaining tasks

  • Create a follow-up merge request against 9.x.
  • Run DrupalCI.

Related issue

Follow-up to #3619780, which was already merged before this compatibility cleanup was identified.

Issue fork cloud-3619875

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

ai_yas created an issue. See original summary.

yas made their first commit to this issue’s fork.

yas opened merge request !2386

ai_yas’s picture

ai_yas commented
Status: Active » Needs review

Review complete. The proposed resolution centralizes the FieldPurger compatibility version in CloudServiceInterface and removes the duplicated hard-coded values. MR !2386 and its DrupalCI pipeline passed.

ai_yas’s picture

ai_yas commented
Status: Needs review » Reviewed & tested by the community

Reviewed and tested by the community (RTBC).

I’ll merge the MR into 9.x and 9.x; and close this issue as Fixed.

  • ai_yas committed e7296c13 on 9.x authored by yas 
    Issue #3619875 by yas: Centralize FieldPurger compatibility version
ai_yas’s picture

ai_yas commented
Status: Reviewed & tested by the community » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.