Suggestion: Tag and publish release versions

[ewrogers]

As updates roll out it can be difficult to differentiate and pin to specific release versions. Especially when trying to build docker containers around versions it essentially has to be done via commit hash when pulling. There's also lack of release note/changelog history here.

Most docker images are based on the master/main branch and just re-pull to latest on startup. While this is convenient for auto-update functionality, it can also be problematic and cause unintended side effects on restarting a container. With the recent 1.0.2 update, there was an issue where the container/image had to be dropped, volume deleted, and restored from backup.

It would be nice releases were tagged in the repo, and release zips available to be downloaded by version. I know releases and hotfixes can be hectic, but it can be confusing as a server admin seeing a few updates trickle in the repo throughout the day. "Should I restart my server? Is the version the same?"

[denizkoekden]

I bump this up. Please do release versions with tags.