revalidateTag without a cacheLife profile

next/revalidate-tag-profilewarningnextjs-16correctness

Why it matters

In Next.js 16 the single-argument revalidateTag(tag) is deprecated: it needs a cacheLife profile for stale-while-revalidate behavior.

Fix

revalidateTag(tag, "max"), or updateTag(tag) in a Server Action when the user must read their own write.

Credit

  • From the Next.js team

    Next.js 16 deprecates single-argument revalidateTag and adds updateTag for read-your-own-writes in Server Actions.

References

See it