Description

Just discovered this issue. If the buildId is different, it will not regenerate another new cache but just serve from the SSR.
This behavior has been like this since 16 or older.

It is kinda surprised to me, because my old system will create another cache for different build. However, I used buildId as part of the cache key as well, so it is actually easier for me to handle multiple versions. With #1771, users can achieve this and avoid issue like deploying a new version, there is no cache until you invalidate previous cache.

I am not sure if we want to change existing behavior, because with this structure, it can only keep one version of cache anyway.

@eneajaho let me know how you think. Thanks!