@vercel/container
27.0.0 · 18 Nov 2026Apache-2.03.8M / weekRepositoryHomepagenpmAtom feed
Upgrading @vercel/container From 8.2.0 to 8.4.0
5 releases in betweenevery note read
Release by release
- New
Bump the ruby buildpack version to 0.2.0
- New
8.3.1nothing new or fixed in the note
- New
Add
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.
- New
- Fixed
Resolve 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.
- Fixed
- Fixed
Serve 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.
- Fixed
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.