Deprecate recursive plugin discovery

Created on 27 August 2025, 16 days ago

Problem/Motivation

Spin-off from 📌 Add the ability to deprecate a plugin namespace Active , see discussion in that issue.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

📌 Task
Status

Active

Version

11.0 🔥

Component

plugin system

Created by

🇬🇧United Kingdom catch

Live updates comments and jobs are added and updated live.
  • Performance

    It affects performance. It is often combined with the Needs profiling tag.

Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @catch
  • Merge request !13096Try adding a deprecation notice. → (Open) created by catch
  • Pipeline finished with Failed
    16 days ago
    Total: 747s
    #583329
  • 🇬🇧United Kingdom catch
  • Pipeline finished with Failed
    16 days ago
    Total: 830s
    #583370
  • Pipeline finished with Failed
    16 days ago
    Total: 723s
    #583389
  • 🇬🇧United Kingdom catch

    Put up a proof of concept MR that causes the gd image effects subdirectory to throw a deprecation error.

    Also had to update the attribute unit test so it doesn't rely on subdirectory behaviour, not sure if that's really the correct fix for this or not, the relationship between the 'module' namespace and the fixtures is a bit weird.

    No deprecation tests yet either.

Production build 0.71.5 2024