[ 
https://issues.apache.org/jira/browse/BEAM-13119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17438197#comment-17438197
 ] 

Robert Burke commented on BEAM-13119:
-------------------------------------

Looks like it's not possible to avoid using subdirectory tags, for largely good 
reasons.

https://github.com/golang/go/issues/34055#issuecomment-777686495

bcmills explains the issue:
If we start out with only a v0.14.0 tag, then users who require … v0.14.0 will 
use that tag. But then what happens if a lib/go/thrift/v0.14.0 tag is added, on 
a different commit, down the road? Proxies will continue to cache and serve the 
original v0.14.0, but new users with GOPROXY=direct will instead see the nested 
tag and get checksum errors.

> Add subdirectory prefixed tags to release process to support Go SDK 
> versioning.
> -------------------------------------------------------------------------------
>
>                 Key: BEAM-13119
>                 URL: https://issues.apache.org/jira/browse/BEAM-13119
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-go
>            Reporter: Robert Burke
>            Assignee: Robert Burke
>            Priority: P2
>
> BEAM-5379 updated the SDK to use modules for Dependency management for 2.33.0 
> but it isn't behaving as expected. The release versions are being ignored.
> Turns out we misunderstood one facet of having the go.mod file not at the 
> root directory: to version that package, version tags must be prefixed with 
> the directory path to the go.mod file. 
> See https://golang.org/ref/mod#vcs-version for the description.
> We've validated that adding such a prefixed tag to a release branch resolves 
> the issue.  
> https://pkg.go.dev/github.com/apache/beam/sdks/[email protected]/go/pkg/beam?tab=versions
> This JIRA is to track adding the version tags to the release processes so we 
> can continue paired releases for all SDKs, and back updating 2.33.0 with a 
> tag so we can keep it as the first "non-experimental" release.
> Further discussion:
> https://lists.apache.org/thread.html/r987ea3540a0457ede258a96a0748b9af39c1de0acd83e822de8d0abb%40%3Cdev.beam.apache.org%3E



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to