next.js

79177b7b - fix: unstable_cache should not cache new result in draft mode (#67772)

fix: unstable_cache should not cache new result in draft mode (#67772) ### What? In draft mode, as of right now, `unstable_cache` does not read from the static store, but still write to it. This leads to the following scenario: 1. Content Editor enters draft mode to test his content 2. Content Editor skips cache and reads preview data 3. Preview data is written to store 4. Random user without draft mode receives preview data until cache is revalidated again ### Why? There's an early exit before reading from the cache - the new result is written to the cache nonetheless though. ### How? New result is only cached if draft mode is disabled. Co-authored-by: JJ Kasper <jj@jjsweb.site>