Collector binary reports wrong version

[pieterlexis-tomtom]

Hey folks,

I just downloaded otelcol contrib 0.115.1 (released about a day ago). However, the binary reports as being version 0.115.0. See below:

/tmp/tmp.VViyajyZAw $ curl -LO https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.115.1/otelcol-contrib_0.115.1_linux_amd64.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 70.4M  100 70.4M    0     0  6353k      0  0:00:11  0:00:11 --:--:-- 8190k
/tmp/tmp.VViyajyZAw $ tar xf otelcol-contrib_0.115.1_linux_amd64.tar.gz
/tmp/tmp.VViyajyZAw $ ./otelcol-contrib -v
otelcol-contrib version 0.115.0

I have some automation in place that checks the currently installed version with the expected version and this breaks now 😉.

[dosubot]

Hey @pieterlexis-tomtom! I'm here to help you with this issue. If you have any questions or need assistance, feel free to ask.

The issue you're experiencing, where the OpenTelemetry Collector binary reports the wrong version, could be related to a problem in the release process where the version number wasn't correctly embedded in the binary. This can happen if the {{ .Version }} template variable wasn't updated properly during the build process ^[1][2].

To resolve this, you might want to check if there has been any recent update or fix related to this issue in the repository or if a new release has been made to correct the versioning error. If the problem persists, it might be necessary to manually verify the versioning in the build configuration files, such as .goreleaser.yaml, to ensure the correct version is being set during the build process.

To continue talking to Dosu, mention @dosu.

[atoulme]

We had to rerun the release, with a new tag, as the first release failed only for the contrib build. Tagging this issue as a release retro item.