Provide a way for plugins to specify the version that annotations are deprecate in

Created on 5 May 2025, 7 days ago

Problem/Motivation

In 📌 Triggering deprecations for plugins using annotations when core plugin type has been converted to attributes Needs work we made the deprecation message for providing annotation versions of plugins deliberately non-specific because the deprecation version depends on the contrib plugin manager.

Opening this to see if we can find a way to make it more specific - for example could we add generic support in plugin attribute classes to add an 'annotations deprecated in' key? Or could we add an optional method to plugin managers to provide a version (and module name?).

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.
Sign in to follow issues

Comments & Activities

  • Issue created by @catch
  • 🇨🇭Switzerland berdir Switzerland

    I think discovery doesn't have access to the plugin manager. But a property on the annotation class for the min version could work, we could add that.

Production build 0.71.5 2024