Lacking IPv6 support on registering new ci runners

I've begun to setup a gitlab-ci-multi-runner instance on an IPv6 only server (hard enough because your repos are IPv4 (legacy) only) but it seems like the ci-runner has some problems registering over IPv6 to my (IPv6 enabled) gitlab.

The versions:

• gitlab-ci-multi-runner version 0.7.2 (998cf5d)
• gitlab 8.3.4-ce.0

The error:

ERRO[0027] <token> Registering runner... failed couldn't execute POST against https://git.example.com/ci/api/v1/runners/register.json: Post https://git.example.com/ci/api/v1/runners/register.json: dial tcp 198.51.100.1:443: network is unreachable 
PANI[0027] Failed to register this runner. Perhaps you are having network problems 

Do you have AAAA record for domain?

Yes for sure and the IPv6 setup is working correct. It was the first thing I checked before writing this issue.

What happens if you do: curl https://git.example.com/ci/api/v1/runners/register.json?

This appears to be problem with Go 1.4 that we use: https://github.com/golang/go/issues/8453

If we migrate to 1.5 it will be resolved.

ok, sounds great can you estimate when you migrate to 1.5?

One or two months from now.

Milestone changed to v1.1

Added ~146290 label

Status changed to closed

We did switch to Go1.5.