megachangelog
Feature

Vercel Container Registry repositories can now be made public

Vercel Container Registry now supports making repositories public, allowing anyone with a Vercel account to pull and use images while maintaining read-only access. Repository visibility can be managed from the project dashboard, CLI, or REST API.

now lets you make a repository public, so anyone with a Vercel account can pull and use its images.Vercel Container Registry

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 , which accepts a team-scoped reference in :Vercel SandboximageSandbox.create()

Update your repository visibility from the dashboard, the CLI, or the REST API, and see the Vercel Container Registry to learn more.documentation

Read more

container-registryimagesaccess-controlapi

Source: original entry ↗