Vercel
Cost
Performance
Missing revalidate / cache option on public data fetch
Part of the Caching & cost check · fix arrives as a guide
What it is
A fetch for public data specifies no revalidate or cache option, so it uses the framework default.
Why it matters
Defaults have changed between framework versions, so whether the response is cached depends on which version you are on. That is not something to leave implicit on a path that runs on every request.
How to fix it
Set the caching behaviour explicitly — next: { revalidate: 60 } or an equivalent — so the intent is stated and survives a framework upgrade.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.