@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
- ?
- changes to make
- 0
- advisories fixed
- 2
- new
- 0
- fixes
Release by release
- 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 ago.modat their root, includingpackage mainand directory service entrypoints.api/**/*.gofunctions and Go handler entrypoints keep using@vercel/go. - New
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.
- New
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.