[Feature] ghcr.io/sipeed/picoclaw is private

[mattn]

🎯 The Goal / Use Case

Make ghcrio.io/sipeed/picoclaw public

💡 Proposed Solution

Turn public on in https://github.com/sipeed/picoclaw/pkgs/container/picoclaw

🚦 Impact & Roadmap Alignment

• This is a Core Feature
• This is a Nice-to-Have / Enhancement
• This aligns with the current Roadmap

🔄 Alternatives Considered

💬 Additional Context

[james2doyle]

Just encountered this myself too. It would be nice to be able to use this in my homelab without cloning or having to do a full build

[mattn]

I created a container image. I'm pushing it as-is after running docker build.

image: https://github.com/users/mattn/packages/container/package/picoclaw
helm chars: https://artifacthub.io/packages/helm/picoclaw/picoclaw

This is just a temporary fix for me until the official version is released.

[nikolasdehor]

+1 on making the container image public. Having ghcr.io/sipeed/picoclaw as private forces users to either build from source or use the binary releases. A public image would significantly simplify Docker/Kubernetes deployments.

The docker-compose.yml in the repo already references the image — it should "just work" once the registry visibility is flipped to public in the GitHub Package Settings.

@mattn's request is reasonable: Settings → Packages → picoclaw → Change visibility → Public.

[ForceConstant]

Any updates on this? Would love a public release that corresponds to releases versions.

[james2doyle]

Maybe @alexhoshina or @yinwm could bump this?

[alexhoshina]

Maybe @alexhoshina or @yinwm could bump this?

I will notify the relevant personnel.