I don't know the article - but as far as I know it will replace in first next network interaction (going to other page, refresh etc.). If you want to show "There is new version" dialog you need to make an service-worker for this to check version in background.

So I'm gonna observe this thread if anyone knows anything about that as this got my attention haha

Every time you build, most of chanks names get a new name.
So there are 2 options i see here:
1 deploy remove old chanks
2 deploy simply add new chunks and leave previous

So imagine a user work on site and new version files arrived.
His browser keep old one in cache and he will notice nothing,
BUT. In case. his browser did not got all the files it need, it might try to download it. And this is a point we meet these 2 options: do you remove old files or do you keep it?

From what I had seen - previous deployment chunks can't be accessed as each deployment is separated from others (domain is pointing to another "server" then was before). But there is still some possibilities that Vercel is assigning traffic via ray IDs or anything other - but it's depending now on platform itself :/

Finally, I found it: it was called Skew Protection 👍
Thank you!

How that supposed to work in selfhost

it doesn't work in self host. you need to implement your own skew protection.

I think this is valid pattern to solve the issue