Release the Go module

[dunglas]

Because the Go module isn't at the root of the repository but in a subdirectory, the Go module requires a specific tag to be available on Go Packages: go-watcher/vX.Y.Z, where X.Y.Z is the version.

We can either create the same versions as for the main repository or create specific versions just for the Go module.

Could you do please create this tag @e-dant?

[dunglas]

Friendly ping.

[e-dant]

Thanks for the reminder, I'll try to look at this tomorrow.

It should be easy enough to add this to the tool/release script and keep that tag up to date.

Alternatively, wondering if it's possible to place to Go module file in the root of this repository. That's what Rust and Python do for compatibility.

[e-dant]

Hoping that 0b8aea5 solves this. If not, we'll add some tags to this repo and revert that commit.

[dunglas]

@e-dant it looks like it's working properly, with the downside that Go downloads the full repo instead of just the Go code.

[e-dant]

is the current approach acceptable for the time being?

[dunglas]

Couldn't we create a script or a GitHub actions workflow creating the Go tag automatically? It would be better than downloading the full repo.

[dunglas]

Actually, this still doesn't work because tags aren't prefixed by v (0.14.4 instead of v0.14.4): https://go.dev/doc/modules/version-numbers

[e-dant]

Sorry about the delay here. I'll get this fixed up soon. My original hesitation with the go-specific tags was purely for the sake of simplicity in version tagging, the tags read/look/list well right now, being simpler numeric release numbers without clutter. I think I would prefer to replace them with "vX.Y.Z" (instead of "X.Y.Z") rather than "go-watcher/X.Y.Z" and have just one set of release version tags, if the cost of carrying along the rest of the repository is acceptable, although I understand that's a real trade off.