Zotero 10 feature freeze — update your plugins

[Dan Stillman]

Zotero 10 is now feature frozen.

If you're a plugin developer, you should check your plugin's compatibility with the latest beta and fix any remaining issues. You can then set `strict_max_version` in your plugin's manifest to `10.0.*`. If no changes are required, you can simply update `strict_max_version` in your plugin's update manifest without releasing a new version.

We've added many new features, all announced at the top of the forums. There are also lots of internal changes, and we're currently updating Zotero 10 for Developers with the most relevant ones. In particular, note the changes around multi-collection selection, which mean your code can no longer assume that only one source row is selected. Getters like `ZoteroPane.itemsView.collectionTreeRow` will now throw and say to use `collectionTreeRows` instead, and the same for the `collectionTreeRow` property of some contexts on the Zotero.MenuManager API for plugins.

As a reminder, you shouldn't set strict_max_version to a version higher than 10.*, and you shouldn't update it during a beta cycle until we've made an announcement like this and you've tested your plugin against a feature-frozen beta. In the future, we'll block plugins that do so, as they risk breakage or even data loss on users' machines.

We'll continue to make bug fixes until Zotero 10 is released, so please continue to test against the beta.

- Dan