What about server admins using not-yet-released code?

[rugk]

What if server admins use the master branch from the GitHub repo to clone and update their instance? This would let to a failure with this add-on.

Options:

• Ignore them, they should run stable versions
• Include also the hashes for these dev version in the JSON

[nitmir]

One solution would be to put every new commit on a dev branch, and to only merge with master on release. Hence master would be the last released version.

[rugk]

Or, which is easier to manage - to have a develop branch as the branch where pushes/PRs go to. However I like master very much as a default, so it would also be possible vice versa: A stable branch where only stable updates are provided.
A similar discussion about this has happened in PrivateBin/PrivateBin#84.