mmorel-35 commented on PR #115: URL: https://github.com/apache/skywalking-data-collect-protocol/pull/115#issuecomment-3315749068
The proposal to publish to Bazel Central Registry (BCR) does not require changes to the established ASF release process. The workflow operates after a release is tagged and the source tarball is produced according to ASF policy. Bazel Central Registry stores metadata that references the externally hosted source tarball (for example, the GitHub release asset), and does not duplicate or host the tarball itself. The only additional requirement is the use of a GitHub Personal Access Token, configured once by repository maintainers, to enable automated publication to BCR. Minimal ongoing maintenance is expected. Once the workflow is set up, each tagged release is automatically registered in BCR. For each new version, an approval is required in the BCR repository, ensuring compliance and quality for the registry. No fundamental changes to agent builds or compatibility policies are necessary. The primary benefit is improved dependency management for downstream projects such as cpp2sky and others. By registering with BCR, these projects can retrieve skywalking-data-collect-protocol directly from the registry, avoiding repetitive use of git_override in Bazel MODULE files and streamlining integration across the ecosystem. This addition enhances visibility and usability for the protocol with negligible impact on release or maintenance procedures. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
