I guess this is no surprise, but we need to do something to make our release notes match up with our releases to docker hub.
For example, a few days ago the changelog says we released version 0.3.0. That's cool, but we stopped tagging our docker builds that way and instead use git hashes now.
This doesn't affect us in prod because we just deploy the correct tag from docker when we deploy, BUT for anybody reading our release notes, this is not good, since they can't choose which version they want.
I guess we need to either:
Go all in on the git hashes and start putting them into the release notes (and thus give up semantic versioning).
Figure out how to put the version number into the repo somehow and make sure that we remember to update it when needed. Also, add the tag to the builds we push to docker.
I guess this is no surprise, but we need to do something to make our release notes match up with our releases to docker hub.
For example, a few days ago the changelog says we released version 0.3.0. That's cool, but we stopped tagging our docker builds that way and instead use git hashes now.
This doesn't affect us in prod because we just deploy the correct tag from docker when we deploy, BUT for anybody reading our release notes, this is not good, since they can't choose which version they want.
I guess we need to either: