Can we create releases for new updates and assoicate the version with docker image?

[Splinter7914]

This way we can determine what is being changed and decide to get updates as needed. Currently it makes difficult to determine what version one is running and what the changes it might pick up.

One can also subscribe to release updates from github to get notified when new releases get pushed out and users can pick and choose when they want to update.

We can still also use the latest tag to pick up latest release if needed.

[arabcoders]

Hello @Splinter7914 ,

Thank you for your suggestion, i already tag each release with date, most notable changes are documented in README.md with a date, so any version at or past the date includes the changes. isn't that sufficient? honestly i haven't thought match about version numbering as most of the updates are fixes and rarely new features. and most if not all changes and features are backward compatible to not break people setup.

Except in rare cases where i deprecate a feature i usually announce it in advance using the news in README.md, and after the announced deprecated date i usually also announce the removal of said thing.

If that's not enough could you please expand little on what's wrong with sticking with specific version and read the news once in a while if an update worth it =)

[Splinter7914]

regarding source code and container it does not have to right?. Most services I am using their container tags and release page are 1-1. We can use release tag as the tag to publish the docker image in the workflow so it would match

We do not need to make the service change for version. I often use github email notifications to know when a new release available and see what changed to see if I should update or just follow along releases even if I am not actively using the service. For example I was not running watchstate because of multi user support. So when I saw that update in the issue I decided let me try single user again and if that works try mutli user.

So changes in the service would not have helped me in this case. If this is not something we find useful then we can just skip it :).

[arabcoders]

Ah, i understand now what you mean... the release page acts as CHANGESLOG while referencing the changes , i'll see how i could implement auto release tagger with my current setup.

[Splinter7914]

Yup more so just a change log of features/fixes being done. I never really look at the change log but its there I am curious or want to learn with the benefit of being able to use github notifications on releases to get notified.

[arabcoders]

You should be happy now https://github.com/arabcoders/watchstate/releases

[Splinter7914]

Certainly, I already got an email :).

[arabcoders]

Hopefully the auto releaser doesn't spam people with the entire changes and this only because it was first actual release.