Consider uploading the modules outside of github actions artifacts?

Is your feature request related to a problem?

I'm trying to download a "stable" version of the module in a way that doesn't rely on some developer putting the .so file on their desktop machine & uploading it somewhere else; thought I could use your github build artifacts in our build process for that, but unfortunately, that doesn't work: You need a github OAuth app with actions:read scope to do that:

:;    curl https://api.github.com/repos/open-telemetry/opentelemetry-cpp-contrib/actions/artifacts/121064851/zip
{
  "message": "You must have the actions scope to download artifacts.",
  "documentation_url": "https://docs.github.com/rest/reference/actions#download-an-artifact"
}

Describe the solution you'd like
Ideally, there would be a release with attached binaries that I could use (-8

Describe alternatives you've considered

Outside of a release, maybe there's a way to host these artifacts somewhere else; I guess I could also download them into an S3 bucket (but then, again: The data would hit developer machines before being passed on...), or build the module from source.

Start by inspecting the repository's GitHub Actions artifact setup and any existing release configuration. Clarify which module and .so binaries need stable distribution, then define a release-based or external-hosting workflow that avoids requiring OAuth access to Actions artifacts. Done means users can download the intended binaries without relying on developer machines.