github repo release info is very strongly cached in a vivaldi tab

[wez]

This is likely a browser implementation quirk and not a problem with mkdocs-material, but it did send me down a rabbit hole for half an hour last night, so I felt like sharing here.

I keep my docs open in the same browser tab in my browser (vivaldi). I noticed last night that the tag it showed there was an old tag from 2023, rather than the current release. No amount of refreshing or reloading made it update, or even restarting the browser, so I wondered if there was some kind of weird build-time caching, but I didn't see anything extra in the code (

mkdocs-material/src/templates/assets/javascripts/components/source/facts/github/index.ts

Line 60 in 1357cd2

export function fetchSourceFactsFromGitHub(

) which is just doing some fetching via the browser.

What I found was that if I opened a new tab, that would reflect the current and correct release.
This sort of behavior is a bit surprising to me!

Like I said: I think this may be more of a vivaldi issue (which is maybe also a chrome issue?) than a mkdocs issue, because I've seen something like this with sites that transition from a self-signed cert to a let's-encrypt cert. They continue to flag the cert as bad until a new tab is opened.

Make of this what you will!