next.js
fetch cache: revalidate should take precedence over force-dynamic
#72357

Merged

fetch cache: revalidate should take precedence over force-dynamic #72357

ztanner merged 1 commit into canary from 11-05-add_cache_warning_when_using_force-dynamic_revalidate

ijjk added created-by: Next.js team

ijjk added tests

ijjk added type: next

ztanner force pushed from fb49b3cb to 9c935aca 1 year ago

ztanner force pushed from 9c935aca to 18692a1c 1 year ago

ztanner marked this pull request as ready for review 1 year ago

ztanner requested a review from

ijjk 1 year ago

ztanner force pushed from 18692a1c to bb2a65cd 1 year ago

ztanner force pushed from bb2a65cd to 8c6d4276 1 year ago

ztanner changed the title ~~add cache warning when using force-dynamic + revalidate~~ fetch cache: revalidate should take precedence over force-dynamic 1 year ago

ijjk approved these changes on 2024-11-06

ztanner changed the base branch from 11-05-bugfix_revalidate_force-cache_should_work to graphite-base/72357 1 year ago

ztanner changed the base branch from graphite-base/72357 to canary 1 year ago

positive revalidate values should override force-dynamic in fetch cache

fecc719a

ztanner force pushed from 8c6d4276 to fecc719a 1 year ago

ztanner merged 19f93c89 into canary 1 year ago

ztanner deleted the 11-05-add_cache_warning_when_using_force-dynamic_revalidate branch 1 year ago

github-actions added locked

github-actions locked as resolved and limited conversation to collaborators 1 year ago

Reviewers

ijjk

Assignees

No one assigned

Labels

type: next created-by: Next.js team locked tests

Milestone

No milestone

next.js fetch cache: revalidate should take precedence over force-dynamic #72357 Merged

fetch cache: revalidate should take precedence over force-dynamic #72357

next.js
fetch cache: revalidate should take precedence over force-dynamic
#72357

Merged