@vercel/container
27.0.0 · 18 Nov 2026Apache-2.03.8M / weekRepositoryHomepagenpmAtom feed
Summary· from the note as AI read it
Migration neededRead before upgrading: 1 change to make.
Before you upgrade
- Rename VERCEL_GO_TARGET to VERCEL_ENTRYPOINT; zero-config Go projects need a recognized entrypoint
New
- Build daemon images with the Go and Rust buildpacks. A buildpack daemon gets its own image repository and cache, and has
commandbaked into the image. When its buildpack fails, the build names the daemon and its root.
In short
1 new3 internal
Release note
The section about @vercel/container of a note shared by several packages.
Minor Changes
Build daemon images with the Go and Rust buildpacks. A buildpack daemon gets its own image repository and cache, and has
commandbaked into the image. When its buildpack fails, the build names the daemon and its root.Buildpack builds pass the program to build as
VERCEL_ENTRYPOINT, which replacesVERCEL_GO_TARGET: a service's entrypoint, else a zero-config project'sVERCEL_ENTRYPOINTenvironment variable, then for Go the first of@vercel/go'smain.go,cmd/api/main.go, andcmd/server/main.go, and for a zero-config Rust projectsrc/main.rs. A zero-config Go project with none of these fails with that list. An explicit entrypoint takes precedence over aDockerfile.vercelmarker. The Go and Rust buildpacks are pinned at 0.3.0, the first versions that readVERCEL_ENTRYPOINT, and the Ruby buildpack at 0.3.2.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.