Latest showing as v27.0.0 when Github repo shows v26.1.4

[KrazyK786]

Description

When updating github.com/docker/docker to latest, v27.0.0, which from the release information is a pre-release version is pulled down, instead of v26.1.4, which is tagged as latest

Reproduce

go get -u github.com/docker/docker

Expected behavior

Version 26.1.4 is downloaded

docker version

Client:
 Cloud integration: v1.0.35+desktop.13
 Version:           26.1.1
 API version:       1.45
 Go version:        go1.21.9
 Git commit:        4cf5afa
 Built:             Tue Apr 30 11:44:56 2024
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.30.0 (149282)
 Engine:
  Version:          26.1.1
  API version:      1.45 (minimum version 1.24)
  Go version:       go1.21.9
  Git commit:       ac2de55
  Built:            Tue Apr 30 11:48:04 2024
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.6.31
  GitCommit:        e377cd56a71523140ca6ae87e30244719194a521
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client:
 Version:    26.1.1
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.14.0-desktop.1
    Path:     /Users/kristopherjohnson/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.27.0-desktop.2
    Path:     /Users/kristopherjohnson/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.29
    Path:     /Users/kristopherjohnson/.docker/cli-plugins/docker-debug
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /Users/kristopherjohnson/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.23
    Path:     /Users/kristopherjohnson/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.4
    Path:     /Users/kristopherjohnson/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.1.0
    Path:     /Users/kristopherjohnson/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/kristopherjohnson/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.8.0
    Path:     /Users/kristopherjohnson/.docker/cli-plugins/docker-scout

Server:
 Containers: 6
  Running: 0
  Paused: 0
  Stopped: 6
 Images: 43
 Server Version: 26.1.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: e377cd56a71523140ca6ae87e30244719194a521
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.6.26-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 10
 Total Memory: 7.657GiB
 Name: docker-desktop
 ID: 71e08167-6ea6-4b63-ae72-0ac8f8d8e2a5
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Labels:
  com.docker.desktop.address=unix:///Users/kristopherjohnson/Library/Containers/com.docker.docker/Data/docker-cli.sock
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

Additional Info

No response

[cpuguy83]

Thanks for reporting, there was some issue when releasing 27.0.0-rc.1 and go modules picked up the version very quickly.
I believe @thaJeztah is looking into this.

[ankon]

There seems to be something ugly going on here with tags: Earlier my dependabot said "there's a v27.0.0, and the tests pass" so we merged it. Now it turns out that tag is gone???

That breaks builds for everyone that hadn't fetched that tag into their local cache it seems.

$ go mod tidy
go: github.com/docker/[email protected]+incompatible: reading github.com/docker/docker/go.mod at revision v27.0.0: unknown revision v27.0.0

[vvoland]

The release was mistakenly created with a v27.0.0 tag (making Github create it) instead of the v27.0.0-rc.1 tag that was automatically created by our release pipeline. There's no final v27.0.0 yet and we'll going to release it as v27.0.1 instead, due to v27.0.0 being already picked up by the GoSum database.

Please revert back your Go module version to v26.1.4 or upgrade to the v27.0.0-rc.1 instead.
We plan to release the final v27 as v27.0.1 in the next week.

Sorry for the trouble! ❤️

[trivialkettle]

The new version is also released to the arm64 apt repos

apt-cache madison docker-ce
 docker-ce | 5:27.0.0~rc.1-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/test arm64 Packages
 docker-ce | 5:26.1.4-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/test arm64 Packages
...

but not to amd64

apt-cache madison docker-ce
 docker-ce | 5:26.1.4-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable amd64 Packages
...

Sorry if my comment is unrelated, though I came here through the link at https://github.com/docker/for-linux

[vvoland]

In the first case, your repo is set to use the test channel - which also gets the RC releases:

https://download.docker.com/linux/debian bookworm/test arm64 Package

In the latter, the repo is stable, so there's only 26.1.4 which is the latest stable release:

https://download.docker.com/linux/debian bookworm/stable amd64 Package

[vvoland]

v27.0.1 is released now and is picked up as the latest version instead of the v27.0.0.

Let me close the issue.