Packages

@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

Other targets from 8.2.0Latest27.0.0
0
changes to make
0
advisories fixed
2
new
2
fixes

Release by release

  1. 8.4.0

    22 Sep 20261 new
    • New

      Bump the ruby buildpack version to 0.2.0

  2. 8.3.1nothing new or fixed in the note

  3. 8.3.0

    21 Sep 20261 new
    • New

      Add VERCEL_BUILDPACK_PRERELEASE_URL to build with an unreleased buildpack. Set it to the full HTTPS URL of a vercel-<name>-<version>.cnb archive. The builder verifies it against the adjacent .cnb.sha256 file 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.

  4. 8.2.2

    18 Sep 20261 fix
    • 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.

  5. 8.2.1

    17 Sep 20261 fix
    • 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 /_svc routes as container-reachable proxy aliases. The ports can be pinned with --queue-port and --runtime-cache-port; otherwise occupied defaults are incremented automatically. A RUNTIME_CACHE_ENDPOINT you set yourself still takes precedence.

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.