Release v0.11.5?

[ottok]

Hi,

TiUP has been using a pre-release of v0.11.5 since pingcap/tiup@f56aa64.

Could this repo tag an official release v0.11.5 so TiUP can use again an actual release?

Thanks!

CC: @dveeden

[dveeden]

I'll ask somone

[ottok]

Currently the version I uploaded to Debian is based on the git release tag 0.11.4 and I had to apply these two patches to make it compatible with Go versions and libraries in Debian:

• https://salsa.debian.org/go-team/packages/golang-github-pingcap-errors/-/blob/f250c81549ed78342d5c7bba90009f2a7356f1a9/debian/patches/fix-stack_test-failures.patch
• https://salsa.debian.org/go-team/packages/golang-github-pingcap-errors/-/blob/f250c81549ed78342d5c7bba90009f2a7356f1a9/debian/patches/fix-test-expectations-for-paths.patch

These patches are likely unnecessary if this library makes a v0.11.5 release, and TiUP starts to use the new v0.11.5 release, and we can have in Debian officially the v0.11.5 release of this version and TiUP v1.6.x.

None of this is urgent. I am just recording it here in a GitHub issue in case anyone else tooks at TiUP and tries to figure out what is the state of the dependencies and releases, and for upstream and myself to clarify what the state is. That information will be relevent when updating this Go module in the future.

[dveeden]

Do you have a PR for those patches, or are they not needed with the latest master?

[ottok]

Both patches above are due to Debian having different Go libraries available (Debian builds ignore the go.mod versions and go.sum) and did not happen on vanilla upstream build. They could however be upstreamed if they are backwards compatible. I haven't tested it, will do that some later day when done with round of updates elsewhere.