jaredwray/keyv
### [`v3.0.0`](https://togithub.com/jaredwray/keyv/releases/v3.0.0)
The data structure is now normalized across all data stores. Previously there was a difference between how native TTL supporting stores and non TTL supporting stores stored data.
This is a breaking change because if you were previously using Keyv with the Redis or MongoDB adapter, Keyv v3 won't be able to read your data. There are zero API breaking changes though, if you clear your store, Keyv will continue to work with no code changes required.
Moving forward this breaking change will allow us to add opt in changes to data structures for performance improvements in certain use cases without breaking backwards compatibility.
It also makes it much easier to implement data migration tools for automatically transfering data from one Keyv store to another.
More info on the data structure change here: [https://github.com/lukechilds/keyv/pull/29](https://togithub.com/lukechilds/keyv/pull/29)
### [`v2.0.3`](https://togithub.com/jaredwray/keyv/compare/v2.0.2...93567ec5ec4cff719028bd87360b8d2766cdcd02)
[Compare Source](https://togithub.com/jaredwray/keyv/compare/v2.0.2...93567ec5ec4cff719028bd87360b8d2766cdcd02)
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, click this checkbox.
This PR contains the following updates:
^2.0.2
->^3.0.0
Release Notes
jaredwray/keyv
### [`v3.0.0`](https://togithub.com/jaredwray/keyv/releases/v3.0.0) The data structure is now normalized across all data stores. Previously there was a difference between how native TTL supporting stores and non TTL supporting stores stored data. This is a breaking change because if you were previously using Keyv with the Redis or MongoDB adapter, Keyv v3 won't be able to read your data. There are zero API breaking changes though, if you clear your store, Keyv will continue to work with no code changes required. Moving forward this breaking change will allow us to add opt in changes to data structures for performance improvements in certain use cases without breaking backwards compatibility. It also makes it much easier to implement data migration tools for automatically transfering data from one Keyv store to another. More info on the data structure change here: [https://github.com/lukechilds/keyv/pull/29](https://togithub.com/lukechilds/keyv/pull/29) ### [`v2.0.3`](https://togithub.com/jaredwray/keyv/compare/v2.0.2...93567ec5ec4cff719028bd87360b8d2766cdcd02) [Compare Source](https://togithub.com/jaredwray/keyv/compare/v2.0.2...93567ec5ec4cff719028bd87360b8d2766cdcd02)Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.