Zutilo not upgraded to latest version

dstillman

This discussion was created from comments split from: A faster release cycle for Zotero.

iagogv

The worst thing is that Zotero automatically updates, but it doesn't do with plugins. For example, I have installed Zutilo 4.2.0. Zotero upgraded to version 9 today, but it didn't upgrade Zutilo to 4.2.1, which was released one month ago. In this sense, Zotero behaviour is becoming more annoying with time, such as Windows updates.

poettli

To me it is the responsibility of the user to regularly check if the plugins they installed are up-to-date. (And to be sure "Update Plugins Automatically" is checked.)

iagogv

I cannot find now "Update Plugins Automatically", but "Allow automatic updates" is checked for every plugin, and I even tried "Check for Updates", but Zotero does not find anything

dstillman

Because the Zutilo developer didn't properly make the update available. The update manifest currently lists 4.2.0 as the latest version, and 4.2.0 is only compatible with Zotero 8. Zutilo 4.2.1 is available for download but isn't in the update manifest. You should report this to the Zutilo developer.

(Zotero updates plugins automatically by default, and you don't need to change any settings for it to work properly. But it can only update to versions that have actually been made available.)

iagogv

I do not know where is the file you links, but I see that the release version 4.2.1 is at commit ac1deaa

https://s3.amazonaws.com/zotero.org/images/forums/u6735168/0iqxb0r8j46f953c9je2.png

and the updates.json file at that commit includes version 4.2.1 with Zotero 9 as strict max version (https://github.com/wshanks/Zutilo/commit/ac1deaa780d7a8c53a6496604731731ebd614636#diff-d25a0afba407008b3e28db4fd5c91555bb1e34f651e9f0f956470edb7fa85dd4)

And also, https://raw.githubusercontent.com/wshanks/Zutilo/refs/heads/master/deploy/updates.json

adamsmith

The way plugins update is that the manifest.json (included in the root of every plugin) defines the location of the updates.json which is automatically checked for new versions.
Will has this set up so that the relevant updates.json one is the one in the "release" branch of the repository -- that's the one dstillman links to and it doesn't have 4.2.1
Here's the file in context:
https://github.com/wshanks/Zutilo/blob/release/deploy/updates.json
and here's the the manifest.json
https://github.com/wshanks/Zutilo/blob/master/addon/manifest.json

He'll need to fix this, most easily for now by updating the release branch

iagogv

Thanks for the explanation. It is fixed now!