Is Zotero still enforcing 'strict_max_version" for plugins?

dstillman

This discussion was created from comments split from: Announcing Zotero 10.

tim820

Is Zotero still enforcing 'strict_max_version" for plugins ? I notice I have one plugin (below) where the latest plugin version has this set to 8.*, yet it works fine under Zotero version 9.
https://github.com/paulMrG2/zotero-highlight-descriptions

The reason I ask is that I also have about half a dozen important plugins that do not currently have strict_max_version set for version 10.

dstillman

We still enforce it in release versions, yes. We don't enforce it the Zotero beta.

But that specific plugin has an update manifest that doesn't declare strict_max_version at all, which currently avoids compatibility checking altogether. That's equivalent to declaring a future max-version like "99.*", and as we've warned on the dev list, we'll be blocking plugins that do so in a future version. We'll clarify that the same applies to a missing max-version in the update manifest.

(This is all separate from future changes to try to let plugins that use only sandboxed APIs from needing to bump strict_max_version each release cycle. As long as plugins have full access to Zotero internals, they cannot safely opt out of strict version checks.)