[
https://issues.apache.org/jira/browse/THRIFT-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed THRIFT-5205.
----------------------------------------
Resolution: Fixed
Releases carry the v prefix: v0.12.0 through v0.24.0 are all tagged that way,
so go get github.com/apache/[email protected] resolves.
The root go.mod arrived in 0.15.0 (THRIFT-5358), so every release that supports
module consumption is already reachable by a v-prefixed tag. Releases before
0.12.0 are not tagged with the prefix and predate module support, and retagging
released history is not something the project will do.
Closing as fixed.
> Tag prior releases with "v" prefix for compatibility with go.mod
> ----------------------------------------------------------------
>
> Key: THRIFT-5205
> URL: https://issues.apache.org/jira/browse/THRIFT-5205
> Project: Thrift
> Issue Type: Wish
> Components: Go - Library
> Affects Versions: 0.10.0, 0.11.0
> Reporter: Prashant V
> Priority: Minor
>
> Thrift 0.13.0 uses the tag "v0.13.0", while prior releases do not have the
> "v" prefix. Is it possible to add an additional tag "v0.10.0", "v0.11.0", etc
> for older releases so that Go modules works correctly with them, see
> [https://github.com/golang/go/issues/32945]
>
> We have some projects that use older versions and can't update due to the
> breaking changes where ctx was added as a parameter, so need to use old
> versions, but would still like to use go.mod.
>
> Adding additional tags (the old ones should still be valid) would help
> unblock usage of Go modules.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
