Update opentelemetry-collector-releases version to v0.140.1

[otelbot]

Update opentelemetry-collector-releases version to v0.140.1.

See https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.140.1.

[vitorvasc]

Hi @open-telemetry/collector-approvers! Has the v0.140.1 been released? The otelbot opened this PR, but the link checker is failing because of some 404s:

docs/collector/building/receiver/index.html
  fresh --- docs/collector/building/receiver/index.html --> https://github.com/open-telemetry/opentelemetry-collector/blob/v0.140.1/component/config.go
  hitting --- docs/collector/building/receiver/index.html --> https://github.com/open-telemetry/opentelemetry-collector/blob/v0.140.1/component/config.go
  Non-OK status: 404 --- docs/collector/building/receiver/index.html --> https://github.com/open-telemetry/opentelemetry-collector/blob/v0.140.1/component/config.go
  fresh --- docs/collector/building/receiver/index.html --> https://github.com/open-telemetry/opentelemetry-collector/blob/v0.140.1/receiver/receiver.go#L58
  hitting --- docs/collector/building/receiver/index.html --> https://github.com/open-telemetry/opentelemetry-collector/blob/v0.140.1/receiver/receiver.go#L58
  Non-OK status: 404 --- docs/collector/building/receiver/index.html --> https://github.com/open-telemetry/opentelemetry-collector/blob/v0.140.1/receiver/receiver.go#L58
  fresh --- docs/collector/building/receiver/index.html --> https://github.com/open-telemetry/opentelemetry-collector/blob/v0.140.1/receiver/receiver.go
  hitting --- docs/collector/building/receiver/index.html --> https://github.com/open-telemetry/opentelemetry-collector/blob/v0.140.1/receiver/receiver.go
  Non-OK status: 404 --- docs/collector/building/receiver/index.html --> https://github.com/open-telemetry/opentelemetry-collector/blob/v0.140.1/receiver/receiver.go
  fresh --- docs/collector/building/receiver/index.html --> https://github.com/open-telemetry/opentelemetry-collector/blob/v0.140.1/pdata/ptrace/generated_resourcespans.go
  hitting --- docs/collector/building/receiver/index.html --> https://github.com/open-telemetry/opentelemetry-collector/blob/v0.140.1/pdata/ptrace/generated_resourcespans.go
  Non-OK status: 404 --- docs/collector/building/receiver/index.html --> https://github.com/open-telemetry/opentelemetry-collector/blob/v0.140.1/pdata/ptrace/generated_resourcespans.go
  fresh --- docs/collector/building/receiver/index.html --> https://github.com/open-telemetry/opentelemetry-collector/blob/v0.140.1/pdata/pcommon/map.go
  hitting --- docs/collector/building/receiver/index.html --> https://github.com/open-telemetry/opentelemetry-collector/blob/v0.140.1/pdata/pcommon/map.go
  Non-OK status: 404 --- docs/collector/building/receiver/index.html --> https://github.com/open-telemetry/opentelemetry-collector/blob/v0.140.1/pdata/pcommon/map.go

By checking the https://github.com/open-telemetry/opentelemetry-collector repository directly, the tag v0.140.1 doesn't seem to exist. 🤔

[songy23]

It should be 0.140.0 than 0.140.1

cc @jade-guiton-dd

[chalin]

Right, we've hit this problem before ... a few times. Visit https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.140.1, then visit each of the changelogs. You'll see that the core CL yields a 404.

@tiffany76 - how did we solve this in the past? Did we wait until both releases (contrib and core) were synced on their versions? Do we have an issue open for this already?

If we don't have an issue for this already we should open one. I think that the solution for this repo is to create two versions, one for the contrib and one for the core. Then we'll need to adapt the update script so that it updates only the package version that has actually be changed.

[chalin]

Oh, I didn't pay attention the PR status. I'm glad it hasn't been merged yet. 😅

[tiffany76]

Yes, we have an outstanding issue. It's a little more complicated than core or contrib because there are other release artifacts as well.

In the meantime, I've just been waiting for the next release bot update where CI passes because the version numbers are uniform. 🤷

[jade-guiton-dd]

I don't think that will happen here unfortunately; see this comment on the release issue. We can't modify tags once they've been pushed in core/contrib because Go relies on them, so if the CI triggered by the tags failed, we have no choice but to up the patch version for that specific repo. So in this case, the version that was released is 0.140.0 for the core source release and prebuilt artifacts, but 0.140.1 for the contrib source release.