On the one hand, I think we haven't managed yet to maintain the special "release"/"update" release (which keeps the update.json and update-beta.json manifests) with the release-it approach. As far as I could understand, we replace all assets each time, which would mean losing the update.json manifest when a new beta release is published.
On the other hand, considering that we are using much of zotero-plugin-template features for the development of our plugin, I think it would be simpler to use their release approach too. But open to reconsideration, of course.
This pull request supposedly makes the changes needed to use zotero-plugin release script instead of release-it. It also updates the README according to comments in the discussion linked to above.
As mentioned in https://github.com/diegodlh/zotero-cita/discussions/296#discussioncomment-10801610, I think it may be better to use
zotero-plugin release
script instead ofrelease-it
.On the one hand, I think we haven't managed yet to maintain the special "release"/"update" release (which keeps the
update.json
andupdate-beta.json
manifests) with therelease-it
approach. As far as I could understand, we replace all assets each time, which would mean losing theupdate.json
manifest when a new beta release is published.On the other hand, considering that we are using much of
zotero-plugin-template
features for the development of our plugin, I think it would be simpler to use their release approach too. But open to reconsideration, of course.This pull request supposedly makes the changes needed to use
zotero-plugin release
script instead ofrelease-it
. It also updates the README according to comments in the discussion linked to above.If we do merge this, we may want to remove the "update" release created before: https://github.com/diegodlh/zotero-cita/releases/tag/update