Packages

@vercel/container

27.0.0 · 18 Nov 2026Apache-2.03.8M / weekRepositoryHomepagenpmAtom feed

Upgrading @vercel/container From 12.0.0 to 13.0.0

1 release in betweenevery note read

Other targets from 12.0.0Latest27.0.0
The note of 13.0.0 lists no breaking change or deprecation, which is rare for a major.
  1. 12.0.0yours
  2. 13.0.0target
?
changes to make
0
advisories fixed
2
new
0
fixes

Release by release

  1. 13.0.0

    2 Oct 20262 new
    • New

      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 a go.mod at their root, including package main and directory service entrypoints. api/**/*.go functions and Go handler entrypoints keep using @vercel/go.

    • New

      Build Rust HTTP servers with a root Cargo.toml using the container builder when VERCEL_EXPERIMENTAL_BUILDPACK_RUST=1, selecting the build image from rust-toolchain or rust-toolchain.toml and serving public/ from the root path. API functions and services with explicit file entrypoints continue using @vercel/rust.

1 internal line (docs, tests, tooling) left out.

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.