registry.coder.com shows wrong version

[geiseri]

It looks like what is displayed on the website is the main branch, but the modules only can be accessed by a version tag. This might be an artifact of #157 though. This can cause confusion as the published documentation is not always correct.

[matifali]

As a workaround, @mafredri @kylecarbs we should pin https://registry.coder.com to our latest published tag for now.

But this is an issue too as our bump version in docs workflow triggers after the tag is pushed so the docs would then lag behind the actual published version.

[geiseri]

As much as I HATE adding extra release steps, maybe it is best to have the version manually applied in the README.md metadata since there is a bunch of other stuff there too. One project that does this s vcpkg. They literally have 1000s of packages all kept in the same repository with very good QA on released versions.

[michaelbrewer]

@matifali - can we add a script as part of the release to increment all of the readme?

[matifali]

@michaelbrewer we do have a script but it runs after the release (new tag) is published. We can modify and run it manually just before creating a release and it should solve the issue then.

Additionally we need to point registry.coder.com to latest published tag instead of main.

Thoughts @mafredri ?