Using a translatable string as a category for field type is deprecated in drupal:10.2.0

This can only be done when the project requires 10.2, otherwise it breaks functionality on lower versions.

And it's not just about removing the translate class, categories are machine names now, so it will need to be decided where this fits in the new category system.

Hi,
To maintain compatibility, where categories are represented by machine names, you can define a custom category and use its machine name.

Thanks @himanshu_jhaloya. Manually attaching patches is being phased out, and you should create a patch and Merge Request with the Gitlab integration.

DrupalCI and all patch testing will be turned off on July 1, 2024 →

Postponed until June 2024 when support for D10.1 ends - see #4

That's tricky because EOL for 10.1 might also be when 11.0 gets released (yep, that soon already).

This is what we did in entity_reference_revisions:

/**
 * Implements hook_field_info_alter().
 */
function entity_reference_revisions_field_info_alter(&$info) {

  if (version_compare(\Drupal::VERSION, '10.1.999', '<')) {
    $info['entity_reference_revisions']['category'] = t('Reference revisions');
  }

}

So put the new category into the annotation and then switch back in the info hook.

But looking again at the change, this is even easier. this is no_ui field type, the category was just copy pasted but is useless here as it is, per no_ui = TRUE, never actually shown in the UI.

So, just remove the category, problem solved.

Thanks @Berdir let's try it

Please can someone review/confirm that this fixes the problem?

> Manually attaching patches is being phased out, so perhaps you can create a patch and Merge Request with the Gitlab integration.

Yes but it's not currently working unfortunately see 📌 Use gitlab-ci Needs work

Should be OK IMHO. Didn't test, but there's really not much that you can test as it doesn't show up anywhere ;)

> Manually attaching patches is being phased out, so perhaps you can create a patch and Merge Request with the Gitlab integration.

Yes but it's not currently working unfortunately see 📌 Use gitlab-ci Needs work

Ah yes ... it's a race against time now, since DrupalCI and all patch testing will be turned off on July 1, 2024 → .

If it isn't created already, someone should create a meta "support group" issue for module maintainers struggling with the transition to Gitlab CI tests :)

There's the #gitlab channel on Slack for asking questions, but this might be a bit too advanced for that.

FWIW, this doesn't prevent creating merge requests, they still run DrupalCI tests as well.

Great thanks

Automatically closed - issue fixed for 2 weeks with no activity.