Consider using zotero-plugin release
script instead of release-it
#303
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As mentioned in #296 (comment), 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