@vercel/container
27.0.0 · 18 Nov 2026Apache-2.03.8M / weekRepositoryHomepagenpmAtom feed
Upgrading @vercel/container From 8.2.2 to 8.4.0
3 releases in betweenevery note read
- 0
- changes to make
- 0
- advisories fixed
- 2
- new
- 0
- fixes
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
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.