Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use full semver when tagging releases (v2.x.y, not v2.x) #688

Closed
dtscd opened this issue Sep 2, 2022 · 3 comments
Closed

Use full semver when tagging releases (v2.x.y, not v2.x) #688

dtscd opened this issue Sep 2, 2022 · 3 comments
Labels

Comments

@dtscd
Copy link

dtscd commented Sep 2, 2022

installing with go install github.com/rfjakob/gocryptfs/v2@latest will not recognize the latest release "v2.3", even if explicitly requested by tag. Right now it fetches "v2.2.1" which is in the format it recognizes.

I understand I can use git clone directly. But, perhaps a minor tweak would be alright.
Thanks.

@rfjakob rfjakob added the bug label Sep 15, 2022
@rfjakob
Copy link
Owner

rfjakob commented Sep 15, 2022

Thanks for the report. I was not aware of this limitation in Go's fetching logic.

@rfjakob
Copy link
Owner

rfjakob commented Oct 21, 2022

Pushed tag v2.3.0 (identical to v2.3). Does this fix it?

@rfjakob rfjakob closed this as completed Oct 21, 2022
@rfjakob
Copy link
Owner

rfjakob commented Oct 21, 2022

proxy.golang.org seems happy now:

https://proxy.golang.org/github.com/rfjakob/gocryptfs/v2/@v/v2.3.0.info

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants