Consider uploading the modules outside of github actions artifacts?

[antifuchs]

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.

[antifuchs]

One thing that just occurred to me is that the github action could easily publish to the repo's GHCR (package registry) space using https://github.com/marketplace/actions/github-action-publish-binaries - that will work pretty much identically to the way this repo handles artifacts already, but the resulting binaries will be available for anyone who wishes to automatically install the result.