[Bug]: UI no longer shows Jaeger's build info

[spadger]

What happened?

After upgrading from Jaeger 2.4.0 (UI 1.67.0) to Jaeger 2.5.0 (UI 1.68.0), Jaeger's build info has disappeared from the dropdown

Steps to reproduce

Just inspect the About jaeger menu in v2.5.0

Expected behavior

Jaeger's version, commit and build date should be rendered

Relevant log output

Screenshot

No response

Additional context

No response

Jaeger backend version

No response

SDK

No response

Pipeline

No response

Stogage backend

No response

Operating system

No response

Deployment model

No response

Deployment configs

[yurishkuro]

Previously:

[yurishkuro]

The binary itself does capture the version correctly

$ make build-jaeger
echo "building binary for $(go env GOOS)-$(go env GOARCH)"; CGO_ENABLED=0 installsuffix=cgo go build -trimpath   -o ./cmd/jaeger/jaeger-darwin-arm64   -ldflags "-X   github.com/jaegertracing/jaeger/internal/version.commitSHA=9d1e94cdf08c9cc51bec6d9f9f0248229abcd9a9 -X   github.com/jaegertracing/jaeger/internal/version.latestVersion=v2.5.0 -X   github.com/jaegertracing/jaeger/internal/version.date=2025-05-01T03:05:10Z" ./cmd/jaeger
building binary for darwin-arm64

$ ./cmd/jaeger/jaeger-darwin-arm64 version
2025/05/02 10:42:08 application version: git-commit=9d1e94cdf08c9cc51bec6d9f9f0248229abcd9a9, git-version=v2.5.0, build-date=2025-05-01T03:05:10Z
{"gitCommit":"9d1e94cdf08c9cc51bec6d9f9f0248229abcd9a9","gitVersion":"v2.5.0","buildDate":"2025-05-01T03:05:10Z"}%

So something might have broken in the handshake between the binary and the UI.

[yurishkuro]

Hm, the handshake is fine too, running the recompiled binary directly shows the versions

but the released binary does not contain the version

$ docker run --rm --name jaeger \
  -p 16686:16686 \
  -p 4317:4317 \
  -p 4318:4318 \
  -p 5778:5778 \
  -p 9411:9411 \
  jaegertracing/jaeger:2.5.0 version

2025/05/02 14:45:14 application version: git-commit=, git-version=, build-date=
{"gitCommit":"","gitVersion":"","buildDate":""}%

So this is likely related to some change in the build process (and we should have a test to ensure the release binaries report correct version).

[yurishkuro]

Turns out we already have a fix for this #6990. But the release was done using the invalid path pkg/version

echo "building binary for $(go env GOOS)-$(go env GOARCH)"; CGO_ENABLED=0 installsuffix=cgo go build -trimpath   -o ./cmd/collector/collector-linux-amd64   -ldflags "-X   github.com/jaegertracing/jaeger/pkg/version.commitSHA=7d6c4221934c8579ce4b2814ba2c60211c7eb5d4 -X   github.com/jaegertracing/jaeger/pkg/version.latestVersion=v1.68.0 -X   github.com/jaegertracing/jaeger/pkg/version.date=2025-04-05T08:41:40Z" ./cmd/collector
```
I added #7092 to perform version validation during CI build.