Vercel Container Registry now lets you make a repository public, so anyone with a Vercel account can pull and use its images.
Sharing already granted read access to up to 100 teams, and making a repository public opens that access to every Vercel team rather than a named set. Public access is read-only, so anyone can pull and use the images but cannot push, delete, or otherwise change the repository. Repositories stay private by default.
Make a repository public from the project dashboard under Images → repository → Settings → Public Access, where confirming requires typing the repository name. You can also set visibility from the Vercel CLI:
Public images work like shared images in Vercel Sandbox, which accepts a team-scoped
Update your repository visibility from the dashboard, the CLI, or the REST API, and see the Vercel Container Registry documentation to learn more.
Read more
Continue reading...
Sharing already granted read access to up to 100 teams, and making a repository public opens that access to every Vercel team rather than a named set. Public access is read-only, so anyone can pull and use the images but cannot push, delete, or otherwise change the repository. Repositories stay private by default.
Make a repository public from the project dashboard under Images → repository → Settings → Public Access, where confirming requires typing the repository name. You can also set visibility from the Vercel CLI:
Public images work like shared images in Vercel Sandbox, which accepts a team-scoped
image reference in Sandbox.create():Update your repository visibility from the dashboard, the CLI, or the REST API, and see the Vercel Container Registry documentation to learn more.
Read more
Continue reading...