@vercel/container
27.0.0 · 18 Nov 2026Apache-2.03.8M / weekRepositoryHomepagenpmAtom feed
64 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 27.x · latest line
27.0.0
18 Nov 2026- 26.x
- 25.x
- 24.x
- 23.x
23.0.0
27 Oct 2026Summary· from the note as AI read it
Nothing to change: 2 new, 2 fixed.
Minor Changes
Add an experimental Buildah image store cache, enabled with
VERCEL_BUILDAH_STORE_CACHE=1, so builds reuse images and layers from earlier deployments. Concurrent service builds share one--source-date-epochper deployment so their layers stay reusable.@vercel/build-utilsnow exportsresolveBuildConcurrency().Run container schedule commands through a schedules dispatcher added to the built image.
Patch Changes
Build schedule command images with the schedule's
rootas the build context, and have the dispatcher read the command fromVERCEL_SCHEDULE_COMMANDin the function's environment instead of the image's CMD.Complete a schedule command invocation when a process that left the command's process group keeps its output open, dropping that output after 1s.
Expand HTTP regression coverage for the standalone IPC proxy.
- 22.x
22.0.2
23 Oct 2026Report the runtime preset for services without a framework.
Patch Changes
Report the runtime preset for services without a framework.
22.0.1
22 Oct 2026Support
livenessProbeinvercel.json#daemons.
Patch Changes
Support
livenessProbeinvercel.json#daemons.
22.0.0
22 Oct 2026Only updates a dependency:@vercel/build-utils 15.0.0
- 21.x
21.0.0
20 Oct 2026Emit daemon service bindings in the Build Output API daemon descriptor.
Patch Changes
Emit daemon service bindings in the Build Output API daemon descriptor.
- 20.x
20.0.0
19 Oct 2026Summary· from the note as AI read it
Read before upgrading: 1 change to make.
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.
- 19.x
19.1.1 – 19.1.33 releases that only update dependencies@vercel/build-utils 14.21.3Show each
- 19.1.316 Oct 2026@vercel/build-utils 14.21.3
- 19.1.215 Oct 2026@vercel/build-utils 14.21.2
- 19.1.114 Oct 2026@vercel/build-utils 14.21.1
19.1.0
13 Oct 2026Always enabled buildpack cache. Bump the buildpacks to the latest version with cache support.
- 18.x
18.0.1
9 Oct 2026Accept suffixed Dockerfile and Containerfile names in explicit service and daemon entrypoints.
Patch Changes
Accept suffixed Dockerfile and Containerfile names in explicit service and daemon entrypoints.
18.0.0
8 Oct 2026Only updates a dependency:@vercel/build-utils 14.20.0
- 17.x
17.0.0
6 Oct 2026Only updates a dependency:@vercel/build-utils 14.19.0
- 16.x
16.0.0
5 Oct 2026Reduce buildpack build times on Vercel by overlapping setup and cache restoration and exporting the image and cache in parallel. Move Buildah container cleanup into the background and add debug timings to help identify slow build steps.
Patch Changes
Reduce buildpack build times on Vercel by overlapping setup and cache restoration and exporting the image and cache in parallel. Move Buildah container cleanup into the background and add debug timings to help identify slow build steps.
- 15.x
15.0.0
2 Oct 2026Build top-level
daemonswhenVERCEL_ENABLE_DAEMONS_BOA=1:vercel buildbuilds the project as usual, pushes each daemon's Dockerfile image, and writes a Build Output API descriptor todaemons/<name>/.vc-config.json.
Minor Changes
Build top-level
daemonswhenVERCEL_ENABLE_DAEMONS_BOA=1:vercel buildbuilds the project as usual, pushes each daemon's Dockerfile image, and writes a Build Output API descriptor todaemons/<name>/.vc-config.json.
- 14.x
14.0.0
2 Oct 2026Only updates a dependency:@vercel/build-utils 14.16.0
- 13.x
13.0.0
2 Oct 2026Build standalone Go servers with the Vercel Go buildpack and the container runtime when
VERCEL_EXPERIMENTAL_BUILDPACK_GO=1, instead of running them behind the IPC proxy on Lambda. This applies to zero-config Go projects and Go services with ago.modat their root, includingpackage mainand directory service entrypoints.api/**/*.gofunctions and Go handler entrypoints keep using@vercel/go.The build image is
golang:<version>-bookworm, selected from the newer of the go.modtoolchainandgodirectives. The buildpack defaults toGOTOOLCHAIN=local, so the image's Go builds the module. It compiles the package a service entrypoint names, or else the one@vercel/gowould build, passed asVERCEL_GO_TARGET, and the binary runs on distroless Debian 12.Build Rust HTTP servers with a root
Cargo.tomlusing the container builder whenVERCEL_EXPERIMENTAL_BUILDPACK_RUST=1, selecting the build image fromrust-toolchainorrust-toolchain.tomland servingpublic/from the root path. API functions and services with explicit file entrypoints continue using@vercel/rust.
Minor Changes
Build standalone Go servers with the Vercel Go buildpack and the container runtime when
VERCEL_EXPERIMENTAL_BUILDPACK_GO=1, instead of running them behind the IPC proxy on Lambda. This applies to zero-config Go projects and Go services with ago.modat their root, includingpackage mainand directory service entrypoints.api/**/*.gofunctions and Go handler entrypoints keep using@vercel/go.The build image is
golang:<version>-bookworm, selected from the newer of the go.modtoolchainandgodirectives. The buildpack defaults toGOTOOLCHAIN=local, so the image's Go builds the module. It compiles the package a service entrypoint names, or else the one@vercel/gowould build, passed asVERCEL_GO_TARGET, and the binary runs on distroless Debian 12.Build Rust HTTP servers with a root
Cargo.tomlusing the container builder whenVERCEL_EXPERIMENTAL_BUILDPACK_RUST=1, selecting the build image fromrust-toolchainorrust-toolchain.tomland servingpublic/from the root path. API functions and services with explicit file entrypoints continue using@vercel/rust.
- 12.x
12.0.0
30 Sep 2026Only updates a dependency:@vercel/build-utils 14.14.0
- 11.x
11.0.0 – 11.0.23 releases that only update dependencies@vercel/build-utils 14.13.2Show each
- 11.0.229 Sep 2026@vercel/build-utils 14.13.2
- 11.0.126 Sep 2026@vercel/build-utils 14.13.1
- 11.0.025 Sep 2026@vercel/build-utils 14.13.0
- 10.x
10.1.0
25 Sep 2026Persist buildpack dependency layers between deployments through the CNB lifecycle's directory cache under the repository's
.vercel/cache. Enable withVERCEL_ENABLE_BUILDPACK_CACHE=1. Stop returning the Buildah layer store fromprepareCache, which made the platform drop the entire build cache.
10.0.0
24 Sep 2026Only updates a dependency:@vercel/build-utils 14.12.0
- 9.x
9.0.0
23 Sep 2026Only updates a dependency:@vercel/build-utils 14.11.0
- 8.x
8.3.1 – 8.4.02 releases with no change for you1 dependency update, 1 without a note@vercel/build-utils 14.10.2Show each
- 8.4.022 Sep 2026no note
- 8.3.122 Sep 2026@vercel/build-utils 14.10.2
8.3.0
21 Sep 2026Add
VERCEL_BUILDPACK_PRERELEASE_URLto build with an unreleased buildpack. Set it to the full HTTPS URL of avercel-<name>-<version>.cnbarchive. The builder verifies it against the adjacent.cnb.sha256file and uses it for the matching buildpack in the runtime's group. Other buildpacks keep their pinned releases; missing or invalid prerelease files fail the build.
8.2.2
18 Sep 2026Resolve a pushed image's digest from the registry when the push does not report it, instead of the local image store. Podman keeps locally-built layers uncompressed and gzips them on push, so the uploaded manifest hashes to a different digest than the one in
RepoDigests; prebuilt container deployments then referenced a digest that did not exist in VCR. Both the Docker and buildah engines now fail the build if the pushed digest cannot be resolved rather than emitting a mutable tag.
8.2.1
17 Sep 2026Serve Vercel Queues and Runtime Cache from dedicated local ports in
vercel dev, including projects without configured queue services. Poll-mode consumers can create consumer groups on first receive and read retained messages from the beginning of a topic. Every service, sidecar, function, and framework dev command receives the direct local endpoints, while container services use authenticated/_svcroutes as container-reachable proxy aliases. The ports can be pinned with--queue-portand--runtime-cache-port; otherwise occupied defaults are incremented automatically. ARUNTIME_CACHE_ENDPOINTyou set yourself still takes precedence.
8.2.0
15 Sep 2026Route Ruby services and zero-config Ruby projects (Rails and Rack) to the experimental Ruby buildpack container builder behind
VERCEL_EXPERIMENTAL_BUILDPACK_RUBY=1. The buildpack is selected only when aGemfilesits at the build root and no fileentrypointnarrows the build; services with an explicit.rb/.ruentrypoint keep building with@vercel/ruby.vercel devreports that Ruby projects and services are not supported yet.
8.1.0
14 Sep 2026Add experimental Cloud Native Buildpacks lifecycle support with isolated source staging, pinned lifecycle and buildpack archives, and runtime-owned image resolution. Ruby images are selected from
.ruby-version,.tool-versions, or thetools.rubyentry inmise.toml, then an exact Gemfile declaration, defaulting to Ruby 3.4. Unsupported version declarations fail with configuration guidance. Nothing selects a buildpack yet.
Minor Changes
Add experimental Cloud Native Buildpacks lifecycle support with isolated source staging, pinned lifecycle and buildpack archives, and runtime-owned image resolution. Ruby images are selected from
.ruby-version,.tool-versions, or thetools.rubyentry inmise.toml, then an exact Gemfile declaration, defaulting to Ruby 3.4. Unsupported version declarations fail with configuration guidance. Nothing selects a buildpack yet.
8.0.0
11 Sep 2026Only updates a dependency:@vercel/build-utils 14.10.0
- 7.x
7.0.0 – 7.0.34 releases that only update dependencies@vercel/build-utils 14.9.3Show each
- 7.0.39 Sep 2026@vercel/build-utils 14.9.3
- 7.0.28 Sep 2026@vercel/build-utils 14.9.2
- 7.0.14 Sep 2026@vercel/build-utils 14.9.1
- 7.0.01 Sep 2026@vercel/build-utils 14.9.0
- 6.x
6.0.0
1 Sep 2026Only updates a dependency:@vercel/build-utils 14.8.0
- 5.x
5.0.0
29 Aug 2026Only updates a dependency:@vercel/build-utils 14.7.0
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.