Java Changlogs caching too strongly

[vdvman1]

The /java/changlog page seems to be caching too strongly on the client side, visiting the page after new versions have been released since the last visit doesn't seem to show the new versions in the version list and doesn't show the correct latest changelog until after doing a full refresh (CTRL+F5 in Chrome on Windows)

This has already been fixed server side in c03c9f4, but it seems to be caching client side too much too. Need to investigate exactly why this is and how to fix it

[vdvman1]

After checking the build logs, it appears that next.js is incorrectly detecting /java/changelog as a static page, despite the unstable cache for the latest page having a revalidation time.

It should be possible to solve this by setting

export const dynamic = 'force-dynamic'

or potentially

export const revalidate = 2 /* m */ * 60 /* s/m */

in src/app/java/changelog/page.tsx

[vdvman1]

It does appear to be listed as incremental static regeneration, but that's also the case for the home page which doesn't do any fetching at all, so it's hard to tell when/if Next.JS/Vercel will regenerate the page

There also appears to be a commit related to unstable_cache and static generation in Next.JS on the same day this project was first created, so it's possible that updating Next.JS will fix this issue