build(deps): bump dexie from 4.4.4 to 4.4.5 - #1472
Merged
rubenvdlinde merged 1 commit intoAug 30, 2026
Merged
Conversation
Bumps [dexie](https://github.com/dexie/Dexie.js) from 4.4.4 to 4.4.5. - [Release notes](https://github.com/dexie/Dexie.js/releases) - [Commits](dexie/Dexie.js@v4.4.4...v4.4.5) --- updated-dependencies: - dependency-name: dexie dependency-version: 4.4.5 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
rubenvdlinde
deleted the
dependabot/npm_and_yarn/development/dexie-4.4.5
branch
August 30, 2026 08:01
Contributor
Quality Report — ConductionNL/dossiq @
|
| Check | PHP | Vue | Security | License | Tests |
|---|---|---|---|---|---|
| lint | ✅ | ||||
| phpcs | ✅ | ||||
| phpmd | ✅ | ||||
| psalm | ✅ | ||||
| phpstan | ✅ | ||||
| phpmetrics | ✅ | ||||
| eslint | ✅ | ||||
| stylelint | ✅ | ||||
| build | ✅ | ||||
| check-manifest | ✅ | ||||
| check-vue3-compile | ✅ | ||||
| test-l10n | ✅ | ||||
| format | ✅ | ||||
| check-schema-l10n | ✅ | ||||
| check-l10n-js | ✅ | ||||
| composer | ✅ | ✅ 106/106 | |||
| npm | ✅ | ✅ 552/552 | |||
| app:check-code | ⏭️ | ||||
| info.xml | ✅ | ||||
| REUSE | ❌ | ||||
| PHPUnit | ✅ | ||||
| Newman | ⏭️ | ||||
| Playwright | 🚨 NO VERDICT — enabled but never ran | ||||
| Hydra gates | ✅ |
Quality workflow — 2026-08-30 08:31 UTC
Download the full PDF report from the workflow artifacts.
rubenvdlinde
added a commit
that referenced
this pull request
Sep 1, 2026
…k set (#1636) Dexie throws "Two different versions of Dexie loaded in the same app" at module init when two copies at different versions meet in one page, and the SPA never mounts. The 2026-09-01 acceptance run on a clean rig hit exactly that: dossiq-main.js at 4.4.5 beside a shared nc-vue chunk at 4.4.4, and the Cases page rendered as bare chrome. The version alignment landed in #1472 and in nextcloud-vue#825, which stopped the library vendoring its own dexie. Nothing guarded it: the next dexie bump on either side reintroduces the throw with every instrument green. This adds scripts/check-single-dexie.js as a postbuild step, so it runs wherever npm run build runs, including the shared release workflow. It fails when two built chunks embed different Dexie versions, or when the embedded version is not the one package-lock.json resolves. Verified against a fresh production build (one version, 4.4.5, matching the lockfile, exit 0) and against a planted 4.4.4 chunk (exit 1).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps dexie from 4.4.4 to 4.4.5.
Release notes
Sourced from dexie's releases.
Commits
22bdff1dexie@4.4.56a7b452fix(dbcore): don't crash when an index is named 'constructor' (#2325)dbaf960dexie-cloud-addon@4.4.143fd4745fix(dexie-cloud-addon): fall back to fetchTokens when refresh fails962052fupdated pnpm lockfile12038d1Updated deps of dexie-cloud-todo-appDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)