ocb release artifacts are missing

[edwardxia]

The documentation https://opentelemetry.io/docs/collector/custom-collector/ currently points to https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/cmd%2Fbuilder%2Fv0.132.0/ocb_0.132.0_linux_amd64 which is missing...

Also I'm seeing the release pipeline being changed back and forth that v0.132.x release tags has ocb in release artifacts (e.g. v0.132.0, v0.132.1, v0.132.2), while others are using a separate cmd/builder tag (e.g. cmd/builder/v0.132.4).

We have an automated script handling version update for a custom build, and the script depends on the ocb download to have a fixed url schema. So what's the schema moving forward?

[dosubot]

Hi @edwardxia! I'm Dosu and I’m helping the opentelemetry-collector-releases team.

The ocb (OpenTelemetry Collector Builder) release artifacts are now published under tags in the format cmd/builder/vX.X.X, not the main release tags like v0.132.0. This change was made to decouple builder releases from core collector releases and allow independent versioning and retries without modifying existing tags. Some older releases (e.g., v0.132.2) had ocb artifacts under the main tag due to a bug, but this has been fixed and moving forward, the correct schema is:

https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/cmd%2Fbuilder%2Fv<version>/ocb_<version>_<os>_<arch>

For automation, always use the cmd/builder/vX.X.X tag for ocb downloads. If an artifact is missing, it may be due to a pipeline failure or misconfiguration; re-running the release pipeline usually resolves this. It's best to check the release page for artifact presence before scripting downloads, as the pipeline now supports multiplatform builds and checksums for all targets when successful.
Reference: Tag schema and release pipeline changes
Release workflow details

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[mowies]

The schema didn't change, we had a bug where release assets were attached to the wrong release.
See [Link] for more details.
From 0.132.4 moving forward, everything should be as before.

If you encounter this issue again, please re-open this ticket or create a new one.