You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
Should this process be included in ShardingSphere's official release guidelines?
The text was updated successfully, but these errors were encountered:
linghengqian
changed the title
Push the Docker Image of ShardingSphere Agent 5.5.1 to Github Package
Push the Docker Image of ShardingSphere Agent 5.5.1 to Github Packages
Oct 22, 2024
linghengqian
changed the title
Push the Docker Image of ShardingSphere Agent 5.5.1 to Github Packages
Push the Docker Image of ShardingSphere Agent 5.5.2+ to Github Packages
Oct 22, 2024
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?
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.
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?The text was updated successfully, but these errors were encountered: