|
| Summary: |
Upgrade to dexie 4.4.5 |
| Issue Type: |
 Task |
| Affects Versions: |
1.6.1 |
| Assignee: |
Unassigned |
| Components: |
Dependency Upgrades |
| Created: |
27/Aug/26 16:07 |
| Priority: |
 Major |
| Reporter: |
Manuel Leduc |
| Description: |
v4.4.5: Dexie v4.4.5 Compare Source This is a maintenance release that fixes an issue with indexes named after inherited Object properties and improves authentication recovery in dexie-cloud-addon. Related Package Releases
| Package |
Version |
| dexie |
4.4.5 |
| dexie-cloud-addon |
4.4.14 |
| dexie-react-hooks |
4.4.0 (no change) |
| y-dexie |
4.4.0 (no change) |
| dexie-export-import |
4.4.0 (no change) |
Bug Fixes dexie@4.4.5
- fix: don't crash when an index is named constructor — Tables with a primary key or index named constructor could cause db.open() to fail with TypeError: indexList.push is not a function. The internal index lookup now uses an object without a prototype, avoiding collisions with inherited Object.prototype properties such as constructor, toString, and valueOf. (#2325, fixes #1920). Contributed by @tarann26.
dexie-cloud-addon@4.4.14
- fix: recover from failed refresh-token renewal — When a locally unexpired refresh token is rejected by the server, login() now falls back to the regular fetchTokens authentication path instead of propagating the refresh error. This allows custom authentication integrations to silently obtain new tokens when possible, or trigger their normal login flow when required. OAuth redirect errors continue to propagate normally. (#2326). Fixed by @liz709 and @dfahlander.
|
|
