Vercel Container Registry repositories can now be made public
Vercel has introduced public repositories in its Container Registry, allowing any Vercel user to pull images while maintaining read-only access and default privacy settings.
Vercel Container Registry now supports public repositories, enabling any user with a Vercel account to pull and use container images without requiring explicit team permissions. This expands access beyond the existing read-only permission granted to up to 100 teams, making images available to all Vercel teams by default. Public repositories remain read-only, preventing users from pushing, deleting, or modifying images, ensuring content integrity.
To enable public access, users can navigate to the project dashboard under Images → repository → Settings → Public Access and confirm the change by typing the repository name. This feature is designed to facilitate broader collaboration while maintaining control over who can contribute to the repository.
Public visibility can also be configured via the Vercel CLI, providing an alternative method for users who prefer command-line interfaces. The CLI and dashboard options align with the existing REST API for managing repository visibility, offering flexibility in how users interact with the Container Registry.
The update does not alter the default privacy setting, which remains private for all new repositories. Users seeking more details can refer to the Vercel Container Registry documentation for guidance on managing visibility and access controls.