Are Rollup content hashes a safe caching contract across major upgrades?
We use Rollup's output.entryFileNames and chunkFileNames with [hash] placeholders so browsers and our CDN can cache emitted chunks long-term. This works well within a single Rollup version, but we are unsure what guarantees exist when we upgrade. The documentation describes how hashes are generated from chunk content, but I cannot find a clear statement abou
rollup