We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I was checking rclone's dependencies and when updating pkcs8 I see the following
rclone
pkcs8
$ go get -u github.com/youmark/pkcs8@latest go: downloading github.com/youmark/pkcs8 v0.0.0-20240424034433-3c2c7870ae76 (...) go: upgraded github.com/youmark/pkcs8 v0.0.0-20201027041543-1326539a0a0a => v0.0.0-20240424034433-3c2c7870ae76
It's not pointing to the 1.2 version as go requires using "semver" release numbers X.Y.Z.
https://go.dev/blog/publishing-go-modules
Would it be possible in the future, or for current release, to tag releases with MAJOR.MINOR.PATCH format?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I was checking
rclone
's dependencies and when updatingpkcs8
I see the followingIt's not pointing to the 1.2 version as go requires using "semver" release numbers X.Y.Z.
https://go.dev/blog/publishing-go-modules
Would it be possible in the future, or for current release, to tag releases with MAJOR.MINOR.PATCH format?
The text was updated successfully, but these errors were encountered: