Quick answer: Unity Addressables serving old asset versions after updating the package? The build cache hashes only catalog inputs - bump the player version override or clear the build cache to force a rebuild.
After upgrading Addressables from 1.21 to 1.22 the catalog kept loading pre-upgrade bundles, even though the asset hashes were identical to a clean build.
Clear the build cache
From Window > Asset Management > Addressables > Profiles, run Clear Build Cache > All. This forces a rebuild of every bundle on the next Build Player Content rather than reusing per-bundle hash entries from the previous package version.
Bump the player version override
Set a distinct Player Version Override in the active profile so the catalog filename changes between releases. Otherwise CDNs cache the old catalog and clients never request the new bundles.
Verify with the analyzer
Open Addressables > Analyze, run Check Bundle Dupe Dependencies. Duplicate dependencies are the most common reason a cached bundle silently keeps shipping a stale subgraph after a package upgrade.
“Cache invalidation isn't free on Addressables - changing the package version doesn't bump the bundle hash.”
Pin Addressables to a specific minor in manifest.json so the next time a teammate runs Update Packages the cache assumption doesn't quietly break.