Live Feed/Vercel/Fact Record
Vercel logo
Vercel
feature 92% Confidence Gate September 26, 2026

Vercel Container Registry Adds OIDC-Based Authentication for GitHub Actions

Vercel has introduced the vercel/vcr-action/login GitHub Action to enable image pushes to Vercel Container Registry (VCR) using OIDC tokens. This eliminates the need for long-lived registry credentials by exchanging workflow OIDC tokens for short-lived Vercel access tokens.

Verified State Diff

Comparison Mode:
- Previous State
Users were required to store and manage long-lived registry credentials to authenticate GitHub Actions workflows with Vercel Container Registry.
+ Verified New State
Users can authenticate using the vercel/vcr-action/login action, which utilizes GitHub OIDC to generate short-lived, automatically revoked Vercel access tokens.

Impact & Verification Analysis

WHO IS AFFECTED

Developers using GitHub Actions to build and push container images to Vercel Container Registry.

WHY IT MATTERS

Improves security posture by removing the risk associated with long-lived credentials and simplifies CI/CD pipeline configuration for containerized deployments.

Full Fact Overview

The new vercel/vcr-action/login action allows developers to authenticate with vcr.vercel.com directly from GitHub Actions workflows. By leveraging GitHub OIDC, the action automatically handles the exchange for a short-lived Vercel access token, which is revoked upon job completion. This integration supports Docker by default, with optional support for Podman or Buildah via engine configuration. Users must configure an OIDC policy on their Vercel team and grant the workflow 'id-token: write' permissions to enable this secure authentication flow.

Multi-Source Evidence Chain (1)

Push images to Vercel Container Registry from GitHub Actionshttps://vercel.com/changelog
TRACKED ENTITY
Explore all historical Vercel changes
View Vercel Hub ➔