Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

plugin.json includes min_version and max_version keys #960

Open
pieroit opened this issue Oct 31, 2024 · 2 comments
Open

plugin.json includes min_version and max_version keys #960

pieroit opened this issue Oct 31, 2024 · 2 comments
Assignees
Labels
endpoints Related to http / ws endpoints enhancement New feature or request mad hatter Related to the plugin system

Comments

@pieroit
Copy link
Member

pieroit commented Oct 31, 2024

Have in plugin.json some indication of the versions of core which are compatible with the plugin itself.
It will be up to the plugin developer to keep track of compatible versions.

Same update should be reflected on the registry.

@pieroit pieroit added enhancement New feature or request endpoints Related to http / ws endpoints mad hatter Related to the plugin system labels Oct 31, 2024
@alfredotoselli
Copy link

alfredotoselli commented Nov 5, 2024

I could take this.
We want it just as an info or with enforcement as well? Like plugin activation fails if compatible versions are specified and not matching with the core version in use

@pieroit
Copy link
Member Author

pieroit commented Nov 5, 2024

Thanks @alfredotoselli
Step 1: have it as an info in plugin.json
Step 2: let's talk about enforcing or not here or in a meeting, not sure about it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
endpoints Related to http / ws endpoints enhancement New feature or request mad hatter Related to the plugin system
Projects
None yet
Development

No branches or pull requests

2 participants