-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
go: Tag releases with go/vVERSION #91
Comments
But I should double check this. Also gotta tag the latest releases of Gherkin and Messages |
Check results with https://sum.golang.org/lookup/github.com/cucumber/messages/go/v21@v21.0.1, there may be some delay. |
7 tasks
mpkorstanje
changed the title
go: Tag releases with go/VERSION
go: Tag releases with go/vVERSION
Dec 27, 2022
mpkorstanje
added a commit
that referenced
this issue
Dec 27, 2022
> https://go.dev/ref/mod#vcs-version > If a module is defined in a subdirectory within the repository, that is, the > module subdirectory portion of the module path is not empty, then each tag > name must be prefixed with the module subdirectory, followed by a slash. For > example, the module golang.org/x/tools/gopls is defined in the gopls > subdirectory of the repository with root path golang.org/x/tools. The > version v0.4.0 of that module must have the tag named gopls/v0.4.0 in that > repository. Currently, releases are only tagged with `vVERSION`. So to make go happy we have to add a `go/vVERSION` tag. Fixes: #91
mpkorstanje
added a commit
that referenced
this issue
Dec 27, 2022
> https://go.dev/ref/mod#vcs-version > If a module is defined in a subdirectory within the repository, that is, the > module subdirectory portion of the module path is not empty, then each tag > name must be prefixed with the module subdirectory, followed by a slash. For > example, the module golang.org/x/tools/gopls is defined in the gopls > subdirectory of the repository with root path golang.org/x/tools. The > version v0.4.0 of that module must have the tag named gopls/v0.4.0 in that > repository. Currently, releases are only tagged with `vVERSION`. So to make go happy we have to add a `go/vVERSION` tag. Fixes: #91
mpkorstanje
added a commit
that referenced
this issue
Dec 27, 2022
> https://go.dev/ref/mod#vcs-version > If a module is defined in a subdirectory within the repository, that is, the > module subdirectory portion of the module path is not empty, then each tag > name must be prefixed with the module subdirectory, followed by a slash. For > example, the module golang.org/x/tools/gopls is defined in the gopls > subdirectory of the repository with root path golang.org/x/tools. The > version v0.4.0 of that module must have the tag named gopls/v0.4.0 in that > repository. Currently, releases are only tagged with `vVERSION`. So to make go happy we have to add a `go/vVERSION` tag. Fixes: #91
mpkorstanje
added a commit
that referenced
this issue
Dec 27, 2022
> https://go.dev/ref/mod#vcs-version > If a module is defined in a subdirectory within the repository, that is, the > module subdirectory portion of the module path is not empty, then each tag > name must be prefixed with the module subdirectory, followed by a slash. For > example, the module golang.org/x/tools/gopls is defined in the gopls > subdirectory of the repository with root path golang.org/x/tools. The > version v0.4.0 of that module must have the tag named gopls/v0.4.0 in that > repository. Currently, releases are only tagged with `vVERSION`. So to make go happy we have to add a `go/vVERSION` tag. Fixes: #91
mpkorstanje
added a commit
that referenced
this issue
Dec 27, 2022
> https://go.dev/ref/mod#vcs-version > If a module is defined in a subdirectory within the repository, that is, the > module subdirectory portion of the module path is not empty, then each tag > name must be prefixed with the module subdirectory, followed by a slash. For > example, the module golang.org/x/tools/gopls is defined in the gopls > subdirectory of the repository with root path golang.org/x/tools. The > version v0.4.0 of that module must have the tag named gopls/v0.4.0 in that > repository. Currently, releases are only tagged with `vVERSION`. So to make go happy we have to add a `go/vVERSION` tag. Fixes: #91
mpkorstanje
added a commit
that referenced
this issue
Dec 27, 2022
> https://go.dev/ref/mod#vcs-version > If a module is defined in a subdirectory within the repository, that is, the > module subdirectory portion of the module path is not empty, then each tag > name must be prefixed with the module subdirectory, followed by a slash. For > example, the module golang.org/x/tools/gopls is defined in the gopls > subdirectory of the repository with root path golang.org/x/tools. The > version v0.4.0 of that module must have the tag named gopls/v0.4.0 in that > repository. Currently, releases are only tagged with `vVERSION`. So to make go happy we have to add a `go/vVERSION` tag. Fixes: #91
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From the go docs:
The text was updated successfully, but these errors were encountered: