-
Notifications
You must be signed in to change notification settings - Fork 27.6k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: vercel/next.js
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v14.2.5
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: vercel/next.js
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v14.2.6
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 5 commits
- 25 files changed
- 3 contributors
Commits on Aug 2, 2024
-
[docs] Backport Multi-Zones docs to 14.x branch (#68460)
This makes the Multi-Zones docs available in the live nextjs.org site.
Configuration menu - View commit details
-
Copy full SHA for 28110b6 - Browse repository at this point
Copy the full SHA 28110b6View commit details
Commits on Aug 5, 2024
-
Configuration menu - View commit details
-
Copy full SHA for dc40cc9 - Browse repository at this point
Copy the full SHA dc40cc9View commit details -
Configuration menu - View commit details
-
Copy full SHA for eee87cb - Browse repository at this point
Copy the full SHA eee87cbView commit details
Commits on Aug 21, 2024
-
Ensure fetch cache TTL is updated properly (#69164)
To reduce the number of set requests we were sending upstream we added an optimization to skip sending the set request if the cached data didn't change after a revalidation. The problem with this optimization is the upstream service relies on this set request to know to update the cache entries TTL and consider it up to date. This causes unexpected revalidations while the cache value hasn't changed and the TTL is kept stale. x-ref: NEXT-3693 # Conflicts: # packages/next/src/server/lib/incremental-cache/fetch-cache.ts # test/turbopack-build-tests-manifest.json
Configuration menu - View commit details
-
Copy full SHA for d4ca0b9 - Browse repository at this point
Copy the full SHA d4ca0b9View commit details -
Configuration menu - View commit details
-
Copy full SHA for 427c01d - Browse repository at this point
Copy the full SHA 427c01dView commit details
There are no files selected for viewing