Release tag pointed to old tag

[ekanna]

Release tag pointed to v1.10.0 instead of v1.14.8

[mattn]

Why?

[rittneje]

While go mod only cares about tags (not GitHub releases), for people who are just going by what GitHub calls the latest release, or who have subscribed to notifications about releases, only pushing tags can be misleading.

[ekanna]

I was looking at litestream go.mod file and observed go-sqlite3@v1.14 and when i came to this repo it is showing me v1.10 as latest in release summary. I was wondering how is this possible. Later when i gone through Readme i understand that what github is showing as latest is not latest! So i thought i will let you know. Thanks.

[mholt]

I typically view the latest published release as the last "confident" version of the software, so it might be good to publish a new release about now. :)

Thanks for maintaining this.

[rittneje]

@mattn This seems to be a persistent cause of confusion where developers think they are using the latest version but actually aren't (most recently in #1164). Consequently, I think making GitHub releases would be beneficial.