I published a new version of my module by tagging it and pushing the tag to GH, and immediately tried to xcaddy build with it like xcaddy build --with github.com/infogulch/my-module@v0.0.2, but xcaddy continued to use the old module version. After I manually updated the go proxy service with go get github.com/infogulch/my-module@v0.0.2 then it pulled in the new version. (See https://proxy.golang.org/#faq-new-version)
Some issues:
- I would expect
xcaddy build --with module@version to download new module versions like go get module@version does.
- I would expect xcaddy to complain and fail to build if it didn't find the version I specify, instead of just building with whatever other version it happens to find instead.
I expect this to reproduce with the following steps:
- Create a new module and publish a version
- Create new repo containing a caddy module
- Tag an initial version
git tag -a v0.0.1; git push --tags
- Add it to the proxy
go get my-module@v0.0.1
- Verify that it builds in caddy
xcaddy build --with my-module@v0.0.1
- Publish a new version
git commit ...; git tag -a v0.0.2; git push --tags- Do not manually fetch it with
go get
- Try to xcaddy build with the new version
xcaddy build --with my-module@v0.0.2
- Observe in the build logs that it is still using
v0.0.1
I published a new version of my module by tagging it and pushing the tag to GH, and immediately tried to xcaddy build with it like
xcaddy build --with github.com/infogulch/my-module@v0.0.2, but xcaddy continued to use the old module version. After I manually updated the go proxy service withgo get github.com/infogulch/my-module@v0.0.2then it pulled in the new version. (See https://proxy.golang.org/#faq-new-version)Some issues:
xcaddy build --with module@versionto download new module versions likego get module@versiondoes.I expect this to reproduce with the following steps:
git tag -a v0.0.1; git push --tagsgo get my-module@v0.0.1xcaddy build --with my-module@v0.0.1git commit ...; git tag -a v0.0.2; git push --tagsgo getxcaddy build --with my-module@v0.0.2v0.0.1