@vercel/fs-detectors@6.11.0
Breaking Changes📦 vercel-functionsView on GitHub →
⚠ 2 breaking✨ 4 features🐛 2 fixes🔧 3 symbols
Summary
This release migrates service auto-detection to the V2 format and significantly refines container detection logic, removing support for prebuilt OCI image reference entrypoints.
⚠️ Breaking Changes
- The prebuilt OCI image reference entrypoint has been removed. An `entrypoint` must now explicitly name a Dockerfile or Containerfile; otherwise, the service will error.
- If `runtime: "container"` is specified without an `entrypoint`, it will now only auto-detect the blessed Dockerfile names (`Dockerfile`, `Containerfile`, `Dockerfile.vercel`, or `Containerfile.vercel`). Names like `Dockerfile.prod` are no longer inferred as container entrypoints.
Migration Steps
- If you were relying on an entrypoint that was a prebuilt OCI image reference, you must now explicitly specify the Dockerfile/Containerfile name as the `entrypoint`.
- If you were relying on implicit container detection for non-blessed Dockerfile names (e.g., `Dockerfile.prod`), you must now explicitly set `runtime: "container"` and specify the entrypoint.
✨ New Features
- Service auto-detection has been migrated to the V2 format.
- Layout auto-detect now uses the V2 resolver, generating top-level service-targeted rewrites and per-service path transform routes.
- CLI build and dev server now merge auto-detected rewrites into the route table.
- The `container` framework preset is no longer experimental; projects using `Dockerfile.vercel` or `Containerfile.vercel` markers are now detected as containers without requiring `VERCEL_USE_EXPERIMENTAL_FRAMEWORKS`.
🐛 Bug Fixes
- Refined container detection logic for `services` and `experimentalServicesV2`.
- Ensured `@vercel/container` honors the configured Dockerfile entrypoint instead of defaulting to `Dockerfile` or misinterpreting it as a prebuilt image reference by sharing the set of blessed Dockerfile names (`isDockerfileRef`).