| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| "c8": "^11.0.0", | ||
| "del-cli": "^7.0.0", | ||
| "hot-hook": "^1.0.0", | ||
| "ioredis": "^5.11.1", |
There was a problem hiding this comment.
I don't know if you want your test suite to test both versions or not (I don't think it's worth it), but in a "ideal" world/test coverage scenario, if we want to support both versions, we might want to have e2e tests that cover both.
Sorry, something went wrong.
| "@opentelemetry/core": "^1.30.0 || ^2.0.0", | ||
| "@opentelemetry/instrumentation": "^0.200.0", | ||
| "ioredis": "^5.0.0", | ||
| "ioredis": "^5.0.0 || ^6.0.0", |
There was a problem hiding this comment.
Should we support both or the breaking change is fine?
| "ioredis": "^5.0.0 || ^6.0.0", | |
| "ioredis": "^6.0.0", |
Sorry, something went wrong.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes #22
https://github.com/redis/ioredis/releases/tag/v6.0.0
The main breaking changes are:
queue/package.json
Line 137 in 2ebc06e
This should not impact it either, and if a user ever hit a RESP3 difference, new Redis({ protocol: 2 }) restores the v5 wire protocol.