Version string incorrectly reports 3.2.2 instead of 3.2.3 #18053
Description
Description:
Summary
Erigon v3.2.3 incorrectly reports its version as 3.2.2 in the --version command and P2P networking layer, despite being built from the correct v3.2.3 commit
(a7f74f7eb5835ac445a3a7bf5e33e20ba5e9cb4a).
Evidence
Build Info (Correct ✅)
From container startup logs:
[INFO] Build info git_branch=release/3.2 git_tag=v3.2.3-dirty git_commit=a7f74f7eb5835ac445a3a7bf5e33e20ba5e9cb4a
The build info correctly shows v3.2.3 and the right commit hash.
Version Command Output (Incorrect ❌)
$ docker run --rm erigontech/erigon:v3.2.3 --version
erigon version 3.2.2-a7f74f7e
Expected: erigon version 3.2.3-a7f74f7e
P2P Networking Layer (Incorrect ❌)
From container logs:
[INFO] Started P2P networking name=erigon/v3.2.2-a7f74f7e/linux-amd64/go1.25.4
Expected: name=erigon/v3.2.3-a7f74f7e/linux-amd64/go1.25.4
Impact
- Users cannot easily verify they are running v3.2.3 using standard commands
- Monitoring and version tracking tools will incorrectly identify nodes as v3.2.2
- Creates confusion when validating updates (e.g., ethd version shows 3.2.2 even after updating to v3.2.3)
Root Cause
Based on the https://github.com/erigontech/erigon/blob/main/RELEASE_INSTRUCTIONS.md, the version string should be updated in db/version/version.go for each release. It appears
this file was not updated when the v3.2.3 tag was created, leaving Patch = 2 instead of Patch = 3.
Reproduction
docker pull erigontech/erigon:v3.2.3
docker run --rm erigontech/erigon:v3.2.3 --version
# Output: erigon version 3.2.2-a7f74f7e
# Expected: erigon version 3.2.3-a7f74f7e
Expected Fix
Update db/version/version.go in the release/3.2 branch to set Patch = 3 and rebuild/retag the Docker image.
Environment
- Docker Image: erigontech/erigon:v3.2.3
- Image Digest: sha256:51f699172d06c4254ae40122ed88fafac7331f72309eec13f70ad77bd0cd89d5
- Platform: linux/amd64
- Go Version: go1.25.4
# @