Merge pull request #3189 from micaelmbagira/nestjs-v11-caching-breaking-changes

fix(migration): caching Keyv breaking change

Author: kamilmysliwiec

content/migration.md

@@ -187,6 +187,8 @@ CacheModule.registerAsync({
 
 Where `KeyvRedis` is imported from the `@keyv/redis` package. See the [Caching documentation](/techniques/caching) to learn more.
 
+> warning **Warning** In this update, cached data handled by the Keyv library is now structured as an object containing `value` and `expires` fields, for example: `{{ '{' }}"value": "yourData", "expires": 1678901234567{{ '}' }}`. While Keyv automatically retrieves the `value` field when accessing data through its API, it’s important to note this change if you interact with the cache data directly (e.g., outside of the cache-manager API) or need to support data written using the previous version of `@nestjs/cache-manager`.`.
+
 #### Config module
 
 If you're using the `ConfigModule` from the `@nestjs/config` package, be aware of several breaking changes introduced in `@nestjs/[email protected]`. Most notably, the order in which configuration variables are read by the `ConfigService#get` method has been updated. The new order is: