Moritz Wiesinger

then i think you could go ahead and create a PR adding the receiver to the k8s distro 👍🏼

related to https://github.com/open-telemetry/opentelemetry-collector-releases/issues/866

This will be a bit harder to solve. Git tags are using the timestamp format for the nightly tags, but container images don't have the timestamp and rather use the...

I'm putting this on hold for now. There's still a lot of rough edges around the new implementation and we have a rather advanced setup which is not fully supported...

@bogdandrutu @ChrsMark could you pls take another look at this? 🙏🏼

Yes, this seems to be a bug. Care to contribute a fix for it @BDunneInTheSun @kekjoshi ? Should be easy to just validate against the `dt0s` prefix instead of `dt0s08`.

thanks! i added the code to https://github.com/open-telemetry/opentelemetry-collector-releases/pull/1016 in https://github.com/open-telemetry/opentelemetry-collector-releases/pull/1016/commits/a7c1cb1a8ca3396a9897299ad525c531143e9528 we'll probably only see if it works, when the PR is merged

seems like we had some issues with this, where the bot didn't have access to push changes to the releases repo 🤔 https://github.com/open-telemetry/opentelemetry-collector-releases/actions/runs/16916623152/job/47932017655 i'm not sure if i did some...

Ahh I used `vars.OTELBOT_APP_ID` and not `vars.OTELBOT_COLLECTOR_RELEASES_APP_ID` to get the token. I think that must have been the mistake. And it didn't break because that variable is also defined and...

Using the correct app ID and private key worked now to push changes, but the PR is blocked because EasyCLA is not happy. Anything specific that needs to be done...