Tyler Helmuth

@codeboten no, but it could. For simplicity in that PR I left the `component.DataType` -> `component.Signal` in `component`, but `component.Signal` and `component.PipelineID` can be moved somewhere else. `componentstatus` depends on...

Based on the voting I will move forward with the refactor.

As for addressing the initial ask of this issue, should we make a new module, `pipeline` at the root and put `Signal` and `PipelineID` in there?

With https://github.com/open-telemetry/opentelemetry-collector/pull/10413 merged, I am removing this from the component 1.0 milestone and Collector V1 project.

For security reasons we have no plans to publish images built with anything other than `scratch`, with only the bare minimum needed to run a Collector. If you need to...

Ya changing this workflow is hard because we use goreleaser-pro, which makes testing in forks/local harder. In the future getting access to a goreleaser-pro key would allow testing the actual...

@mx-psi you're right, the release workflow has an extra step in the `prepare` job to upload the artifacts and thats specifically the step that was failing. I'd still prefer to...

Would we want to run `actions/upload-artifact@v4` on each PR tho?

I like that idea. We could tag the image with `-nightly` or something like that.

@dmitryax if we wanted to take advantage of the entrypoint in the helm chart like @jaronoff97 mentioned we'll need to update the container to use `args` instead of `command`.