linghengqian opened a new issue, #33350: URL: https://github.com/apache/shardingsphere/issues/33350
## Feature Request **For English only**, other languages will not be accepted. Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot make decision by current information, we will **close it**. Please answer these questions before submitting your issue. Thanks! ### Is your feature request related to a problem? - No. ### Describe the feature you would like. - At https://shardingsphere.apache.org/document/5.5.1/cn/user-manual/shardingsphere-jdbc/observability/#docker , we have implemented ShardingSphere Agent nightly builds for the master branch, and are located at https://github.com/apache/shardingsphere/pkgs/container/shardingsphere-agent . - Since neither Github Packages nor Docker Hub are official distribution channels of ASF, it should not be a problem to bypass the release process to publish a separate Docker Image to https://github.com/apache/shardingsphere/pkgs/container/shardingsphere-agent . - I assume that PPMC has the authority to do so. ```shell sdk install java 22.0.1-open git clone [email protected]:apache/shardingsphere.git -b 5.5.1 cd ./shardingsphere/ sdk use java 22.0.1-open docker login ghcr.io ./mvnw -am -pl distribution/agent -Prelease,docker.buildx.push -B -T1C -DskipTests -Dagent.image.repository=ghcr.io/apache/shardingsphere-agent -Dagent.image.tag=5.5.1 clean package ``` - The problem is that the `personal access token (classic)` I generated from https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry does not have permission to manipulate the ASF namespace. And I'm not sure who has this authority, all PMCs? Some ASF members? - Should this process be included in ShardingSphere's official release guidelines? -- 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]
