monsqlize 3.3.0 → 3.3.2

package/CHANGELOG.md

@@ -1,18 +1,20 @@
 # CHANGELOG
 
-> Summary index — the newest versioned release details are in [changelogs/v3.3.0.md](./changelogs/v3.3.0.md); the earlier RC note remains an unpublished rehearsal archive.
-> **Last updated**: 2026-08-11
+> Summary index — the 3.3.2 versioned details are in [changelogs/v3.3.2.md](./changelogs/v3.3.2.md). A versioned note does not establish npm publication; check the registry and immutable tag before deployment.
+> **Last updated**: 2026-10-22
 
 ---
 
 ## Unreleased
 
-No changes are currently recorded after v3.3.0.
+The audited cache, query, Model, transaction, sync and lifecycle repairs are assigned to **3.3.2**. See its [versioned notes](./changelogs/v3.3.2.md) and the [next-change staging log](https://github.com/devcodex-labs/monSQLize/blob/main/changelogs/unreleased.md). Untagged checkouts remain release candidates.
 
 ## Version Overview
 
 | Version | Date | Summary | Details |
 |---------|------|---------|---------|
+| [v3.3.2](./changelogs/v3.3.2.md) | 2026-10-22 | Patch: BSON/cache identity, Model invalidation, pagination, transaction/sync lifecycle and upgrade safeguards; availability requires registry/tag verification | [View](./changelogs/v3.3.2.md) |
+| [v3.3.1](./changelogs/v3.3.1.md) | 2026-09-23 | Patch: audited Model, count, transaction, cache, sync, pool, Data Task and SSH corrections | [View](./changelogs/v3.3.1.md) |
 | [v3.3.0](./changelogs/v3.3.0.md) | 2026-08-11 | Minor: static Model schema type inference, schema-dsl 3.0.4, and silent-by-default Pool logging | [View](./changelogs/v3.3.0.md) |
 | [v3.2.0](./changelogs/v3.2.0.md) | 2026-08-07 | Minor: Vector Search APIs, relation-safe Model deletion, and relation projection improvements | [View](./changelogs/v3.2.0.md) |
 | [v3.1.0](./changelogs/v3.1.0.md) | 2026-07-15 | Minor: schema-dsl v3 GA consumption, canonical validation errors, and normalized full-document persistence | [View](./changelogs/v3.1.0.md) |

package/MIGRATION.md

@@ -1,8 +1,69 @@
-# Migration Guide: monSQLize v1/v2 → v3
-
-This guide starts with the v2.0.6 to v3.0.0 upgrade path, then retains the
-v1-to-v2 compatibility notes for older applications. Review every tightened
-contract that intersects your application before changing the installed major.
+# Migration Guide: monSQLize
+
+Start with the 3.3.1 to 3.3.2 upgrade notes for this candidate, then consult the
+older v3 and v1/v2 paths if needed. Review the operational boundaries that
+intersect your application before changing its installed version.
+
+## Upgrade from v3.3.1 to v3.3.2
+
+An untagged checkout is a release candidate; verify the immutable tag and npm
+registry before deployment. The upgrade guide is also available in [English](https://github.com/devcodex-labs/monSQLize/blob/main/docs/en/upgrade-3.3.2.md) and
+[简体中文](https://github.com/devcodex-labs/monSQLize/blob/main/docs/zh/upgrade-3.3.2.md).
+
+- Query, page, totals and bookmark caches now include source/authentication and
+  pool identities. Upgrade all application instances sharing a backend together;
+  old entries are not read, so expect a cold start and plan for refill traffic.
+  No global Redis flush is needed. TTL/cleanup can reclaim old keys. Applications
+  with custom cache-key patterns should use collection invalidation APIs or
+  result-matching descriptors rather than rebuilding internal prefixes from
+  `getNamespace()`.
+- Custom `cursorValueNormalizer` functions need a non-empty stable
+  `cursorValueNormalizerVersion` such as `token-string:v1` to use page caching or
+  bookmark prewarming. Change the identifier when behavior or captured config
+  changes. A per-query function override needs its own version. Without one,
+  queries still run, page caches and automatic bookmark reads are bypassed,
+  prewarming throws `INVALID_ARGUMENT`, and deep jumps can reach `jump.maxHops`.
+  Prefer `cursorTypes` for simple hints. Custom functions restore every cursor
+  field, including `_id`, instead of default Date/ObjectId restoration.
+- Transaction `timeout` / `maxDuration` now bound work before commit starts;
+  commit timing belongs to driver/server limits. For direct `Transaction`
+  construction, use `transactionOptions.maxCommitTimeMS`; high-level helper
+  options do not currently forward this field. Unknown commit results invalidate
+  affected caches conservatively and preserve the original error; they do not
+  imply rollback or permit automatic business-callback replay.
+- Cache refill coordination applies to the same CacheLike object in one process.
+  Cross-process Redis notifications remain eventually consistent. Same-source
+  routes invalidate together when registered on that cache object; host aliases
+  need consistent endpoints or explicit related-route invalidation.
+
+- Shared BSON query-key encoding uses generation `v4`, including effective BSON
+  input/decoding options and native per-occurrence function serialization.
+  Query, aggregate, totals and bookmark entries start cold. The public `bm:v4`
+  prefix is retained, but its hash changes. Use broad invalidation or isolate
+  cache backends during mixed-version operation; exact descriptors use the
+  current generation. JSON-incompatible result modes bypass result caching.
+- Pipeline-based `findPage()` rejects find-only projections such as `$slice`,
+  `$elemMatch` and positional projection with `INVALID_OPERATION`. Ordered
+  `findByIds()` retains one-query native identity for supported projections and
+  rejects combinations that cannot preserve it; `preserveOrder: false` retains
+  native execution. Check the query guides before relying on special `_id`
+  transformations or dynamic BSON decoding maps.
+- Before enabling Change Stream sync on an empty checkpoint store, confirm that
+  a custom store can round-trip the opaque initial operation-time envelope and
+  its canonical EJSON Timestamp. Existing raw resume tokens remain supported.
+  Before downgrade, pause sync and preserve the checkpoint; an older reader
+  cannot treat the initial envelope as a raw token. A persisted event token
+  restores format compatibility only subject to history retention and the
+  older reader's behavior. Never clear the envelope to restart from now.
+- Sync idempotency markers use v2 JSON tuple keys. Stop writers and drain work
+  before upgrade or rollback; preserve the checkpoint, both marker generations
+  and a recovery snapshot. Do not run mixed key-format writers or blindly trust
+  ambiguous legacy concatenated keys. Use target-owned business idempotence for
+  replay unless a finite mapping is provable. Rollback also needs a compatible
+  raw token and a verified target recovery point; do not clear either store.
+
+See the [3.3.2 notes](./changelogs/v3.3.2.md), [cache guide](https://github.com/devcodex-labs/monSQLize/blob/main/docs/en/cache.md)
+and [sync upgrade/rollback guide](https://github.com/devcodex-labs/monSQLize/blob/main/docs/en/sync-backup.md) for details.
 
 ## Upgrade from v3.0.0 to v3.1.0
 

package/README.md

@@ -12,7 +12,9 @@ Quick path: [Installation](https://devcodex-labs.github.io/monSQLize/getting-sta
 Configuration reference: [English](https://devcodex-labs.github.io/monSQLize/configuration) · [简体中文](https://devcodex-labs.github.io/monSQLize/zh/configuration)
 Upgrade and security: [Migration Guide](./MIGRATION.md) · [Private Vulnerability Reporting](./SECURITY.md)
 
-The npm `latest` dist-tag and GitHub Pages are the stable channel; `main` may contain the next release. Pages deployment accepts only a versioned Git tag whose package version is already present on npm, so unpublished APIs are not promoted as stable documentation.
+The npm `latest` dist-tag and GitHub Pages are the stable channel; `main` may contain the next release. Pages deployment accepts only a versioned Git tag whose package version is already present on npm, so unpublished APIs are not promoted as stable documentation. The Google site ownership verification file is copied separately from the workflow commit, with its source commit and content hash recorded in the deployment summary.
+
+This source tree targets **3.3.2**. Its cache, Model, pagination and sync fixes, including cold-cache upgrades and checkpoint rollback limits, are described in the [3.3.2 notes](./changelogs/v3.3.2.md) and [migration guide](./MIGRATION.md). Read the upgrade guide in [English](https://github.com/devcodex-labs/monSQLize/blob/main/docs/en/upgrade-3.3.2.md) or [简体中文](https://github.com/devcodex-labs/monSQLize/blob/main/docs/zh/upgrade-3.3.2.md). Untagged checkouts remain release candidates; verify the immutable tag and requested registry version before deployment. Candidate preparation does not publish npm or update stable Pages.
 
 This development source is pinned to verified registry `schema-dsl@3.0.4`. The v3 package remains subject to the full release gate before an immutable tag and npm publication.
 
@@ -332,6 +334,14 @@ Relative model paths are resolved from `process.cwd()`. In production services,
 Model-declared indexes are still created automatically by default for backward compatibility. Production services can turn off automatic indexing and run an explicit preflight before creating missing indexes:
 
 ```js
+const MonSQLize = require('monsqlize');
+
+async function main() {
+MonSQLize.Model.define('users', {
+  schema: { email: 'email!' },
+  indexes: [{ key: { email: 1 }, unique: true }]
+});
+
 const msq = new MonSQLize({
   type: 'mongodb',
   databaseName: 'mydb',
@@ -339,11 +349,18 @@ const msq = new MonSQLize({
   autoIndex: false
 });
 
-const plan = await msq.ensureModelIndexes({ models: ['users'], dryRun: true });
-
-if (plan.totals.conflicts === 0) {
-  await msq.ensureModelIndexes({ models: ['users'], throwOnError: true });
+try {
+  await msq.connect();
+  const plan = await msq.ensureModelIndexes({ models: ['users'], dryRun: true });
+  if (plan.totals.conflicts === 0) {
+    await msq.ensureModelIndexes({ models: ['users'], throwOnError: true });
+  }
+} finally {
+  await msq.close();
 }
+}
+
+main().catch((error) => { console.error(error); process.exitCode = 1; });
 ```
 
 `ensureModelIndexes()` creates only missing indexes. It does not drop, rename, or rebuild conflicting indexes.
@@ -424,7 +441,7 @@ Cache capabilities include:
 
 - In-memory L1 cache.
 - Optional Redis-backed L2 cache.
-- Automatic invalidation after writes.
+- Opt-in invalidation after writes, including partial bulk-insert failures.
 - Cache namespace, TTL, and distributed invalidation controls.
 
 ## Advanced Capabilities
@@ -444,11 +461,13 @@ await msq.withTransaction(async (tx) => {
 
 Read options such as `session`, `readConcern`, `readPreference`, `collation`, `hint`, `maxTimeMS`, and `allowDiskUse` are forwarded to the MongoDB driver. Query caches are bypassed while a `session` is present, so transaction reads use the driver snapshot instead of a shared cache entry.
 
-Transaction cache invalidations are recorded during the transaction and flushed only after a successful commit. If the transaction aborts, pending invalidations are discarded.
+Transaction cache invalidations are recorded during the transaction and flushed after a successful commit. An unknown commit result also triggers conservative invalidation without reporting rollback or replaying the business callback. If the transaction aborts with a known outcome, pending invalidations are discarded. `timeout` limits work before commit begins; `end()` closes the session and does not commit.
 
 ### Connection Pools
 
 ```js
+const MonSQLize = require('monsqlize');
+async function main() {
 const msq = new MonSQLize({
   type: 'mongodb',
   databaseName: 'main',
@@ -458,7 +477,16 @@ const msq = new MonSQLize({
   ]
 });
 
-const reports = msq.pool('analytics').collection('reports');
+try {
+  await msq.connect();
+  const reports = msq.pool('analytics').collection('reports');
+  console.log(await reports.countDocuments({}));
+} finally {
+  await msq.close();
+}
+}
+
+main().catch((error) => { console.error(error); process.exitCode = 1; });
 ```
 
 ### Change Streams
@@ -512,7 +540,7 @@ The v3 line has been validated against the workspace consumers `chat`, `payment`
 | Surface | Current Support |
 |---|---|
 | Node.js | `>=18.0.0`; CI covers Node 18 / 20 / 22. |
-| MongoDB driver | `mongodb@6.21.0` runtime baseline; driver 7.5.0 has additional compatibility coverage. |
+| MongoDB driver | `mongodb@6.21.0` runtime baseline; driver 7.7.0 has additional compatibility coverage. |
 | MongoDB server | Memory-server based 7.x / 8.x validation is covered by the strict project test matrix. |
 | Module systems | CommonJS and ESM are both validated. |
 | TypeScript | Public declarations are published from `dist/types/index.d.ts`. |

package/changelogs/v3.3.1.md

@@ -0,0 +1,28 @@
+# monSQLize v3.3.1
+
+> Release date: 2026-09-23
+
+## Highlights
+
+This backward-compatible patch closes the post-3.3.0 runtime audit findings. It corrects Model validation, soft-delete, relation and strict-version behavior; count cancellation; transaction, cache, pool and sync lifecycle edges; and backup/restore data fidelity.
+
+## Fixed
+
+- Model writes now surface a schema factory error only when full-document validation is required. Disabling validation or using `skipValidation` no longer blocks unrelated writes and management methods.
+- Boolean soft delete consistently treats only `true` as deleted across reads, batch deletion and relation-usage checks. Hydrated `remove()` follows Model hooks and soft-delete rules.
+- Strict `updateMany` and `updateBatch` preserve the original business filter during each atomic write. A candidate that no longer matches that filter is reported as skipped; a still-matching candidate with a changed version is a conflict. Candidate enumeration is no longer limited by the public find default.
+- Populate pagination applies `skip` and `limit` per parent. Model batch writes, query cache keys, expression evaluation and write-path checks retain their original filters and BSON semantics.
+- Public count operations forward the caller's abort signal to CountQueue, including queued and running work. Running slots remain occupied until the underlying operation settles.
+- Managed transaction aborts reject later wrapped writes. Redis invalidation does not rebroadcast received events, pool close/capacity races are handled, and Change Stream sync preserves resume tokens and failure barriers.
+- Data Task backup/restore preserves canonical BSON values. Optional SSH host verification and local failure cleanup are available without changing the default connection path.
+
+## Compatibility and verification
+
+- No breaking public method signature, package entry point, runtime Node requirement or direct production dependency change. MongoDB remains the only complete adapter; Node.js `>=18` remains the runtime contract.
+- The transitive `fast-uri` override now permits patched v3 releases and resolves to 3.1.8; the development-only `js-yaml` lockfile entry is refreshed to 4.3.2. Both clear high-severity advisories found during release review without changing the supported major versions.
+- Release automation uses npm trusted publishing through GitHub Actions OIDC. The pre-tag check verifies runner readiness; npm verifies the configured publisher during the actual publish.
+- Validation-disabled writes and strict batch-result classification may behave differently from the faulty post-3.3.0 main branch; applications relying on the documented contracts receive the corrected behavior.
+- The root CJS/ESM byte budget moves from 720,000 to 740,000 to cover the audited runtime fixes while retaining a tight size guard. The CLI budget remains 50,000 bytes.
+- The release gate covers full tests and coverage, Node 18/20/22 CI, Node 20/22 × MongoDB Driver 6/7 × MongoDB Server 7.0.37/8.0.26, package installation, and bilingual website verification.
+
+Private SSH and Atlas deployments remain operator-managed integration checks; local and public CI coverage does not claim to replace them.

package/changelogs/v3.3.2.md

@@ -0,0 +1,37 @@
+# monSQLize v3.3.2
+
+> Release date: 2026-10-22
+> Publication authority: the immutable tag and npm registry. An untagged checkout is a release candidate; the date above does not establish registry availability.
+
+## Highlights
+
+This patch consolidates the audited fixes after 3.3.1 for BSON query identity, cache invalidation, Model visibility and writes, pagination, transactions, Change Stream sync and resource cleanup. Public entry points, Node.js `>=18`, direct production dependencies and build formats remain unchanged. Release and docs tooling require Node.js 22.
+
+## Fixed
+
+- Isolate query, page, totals and bookmark caches by data source, authentication identity and pool. Link same-source route invalidation and fence stale in-flight reads and backfills across writes, commits and received invalidation.
+- Preserve effective BSON input and decoding options, ordered document/Map values, undefined, negative zero, binary views and subtypes, inherited BSON settings and cross-realm leaves in shared query identities. Capture functions per native occurrence and preserve Code scope access. Avoid JSON result caching for incompatible result modes or lazy dynamic decoding maps.
+- Align explicit Model aggregate/page invalidation with soft-delete visibility, converted filters and captured execution pipelines. Isolate malformed invalidation descriptors so valid siblings still run; successful writes keep their native results. Automatic invalidation stays off by default, and post-write/post-commit invalidation remains best-effort.
+- Apply supported page projections after custom pipeline stages; reject write stages and unsupported find-only projections. Preserve requested ID order in one native query for supported excluded/computed `_id` projections; reject combinations that cannot retain the original identity. Honor native MongoDB equality, collation and sorting during populate, with documented query-cost boundaries.
+- Preserve schema factory captures, lexical bindings, comments and every ECMAScript line terminator. Correct nested DSL scopes and literals without reinterpreting prepared data. Retain Model business filters through final hooks and atomic writes, strict conflict classification, ID-only projections and soft-delete timestamps.
+- Serialize transaction commit/abort/end, apply work deadlines before commit, and conservatively invalidate uncertain commit results without automatically replaying application callbacks. Invalidate after partial batch writes and report only confirmed inserts.
+- Persist an initial Change Stream operation-time checkpoint before opening an empty-store stream; retain raw-token compatibility, strict failure barriers and target-name uniqueness. Use unambiguous per-target idempotency keys and retry failed owned-resource cleanup without losing ownership.
+- Keep slow-log initialization, queues and diagnostic failures isolated, drain admitted work on close and retain event-time bounds. Preserve remote TTL/tag capabilities and shared L1 invalidation fences. Correct CountQueue handoff, pool startup/close/health/statistics, retryable cleanup, Logger tracing and Data Task compare-and-swap boundaries.
+- Repair bilingual post-publish instructions to initialize and validate packages inside an independent consumer directory. Keep versioned package notes, migration guidance and the bilingual static docs site aligned.
+
+## Upgrade and rollback
+
+1. **Plan a cold cache.** Shared BSON query encoding ends at generation `v4`; query/aggregate results, totals and bookmark hashes change. The public bookmark prefix stays `bm:v4`. Refill results and run `prewarmBookmarks()` where needed; old keys may expire normally. No global Redis flush or business-data migration is required. Use broad invalidation or isolated caches while versions coexist; exact descriptors rebuild the current generation.
+2. **Version custom cursor restoration.** A custom `cursorValueNormalizer` needs a stable non-empty `cursorValueNormalizerVersion` for page/bookmark reuse. Without it, queries execute but those caches are bypassed, prewarming rejects with `INVALID_ARGUMENT`, and deep jumps may hit `jump.maxHops`.
+3. **Check special projection combinations.** Pipeline pagination rejects `$slice`, `$elemMatch` and positional find-only projections with `INVALID_OPERATION`. Ordered ID lookup preserves one native query for supported projections; combinations that cannot retain native identity are rejected. Native `preserveOrder: false` remains available. These are explicit compatibility boundaries, not a promise to support every projection/result-mode combination.
+4. **Preserve sync checkpoints before downgrade.** New empty-store sync startup persists an opaque initial envelope with a canonical EJSON Timestamp. Custom stores must round-trip it. Existing raw event tokens stay supported. Stop sync and preserve its store before downgrade: older readers cannot consume the initial envelope as a raw resume token. A saved event token only restores format compatibility subject to history retention and the older version's behavior. Do not erase the envelope or restart from now.
+5. **Coordinate sync marker upgrades.** Idempotency keys are v2 JSON tuples. Stop writers, drain work and preserve checkpoints, both marker generations and a recovery snapshot. Avoid mixed-format writers. Ambiguous legacy concatenated markers cannot be trusted unconditionally; use target-owned business idempotence and replay unless a finite mapping is provable. Rollback requires the same stop/drain safeguards, a compatible raw token and a verified target recovery point; never clear either store as a shortcut.
+
+Read [MIGRATION.md](../MIGRATION.md) and the upgrade guide in [English](https://github.com/devcodex-labs/monSQLize/blob/main/docs/en/upgrade-3.3.2.md) or [简体中文](https://github.com/devcodex-labs/monSQLize/blob/main/docs/zh/upgrade-3.3.2.md). After publication, the documentation site must deploy from the same immutable `v3.3.2` tag as npm; preparing this candidate does not update the stable site.
+
+## Compatibility and verification
+
+- MongoDB remains the only complete database adapter. No public method is removed or renamed; default invalidation behavior and the documented checkpoint compatibility boundaries are retained.
+- The approved root CJS/ESM budget is 820,000 bytes per artifact; the independent CLI stays at 50,000 bytes. These are build-size gates, not application resource or request limits.
+- Qualification uses the existing full tests, coverage and risk floors, runnable examples, Node 20/22 × Driver 6/7 × MongoDB 7/8 matrix, dataTasks/CLI integration, production dependency audit, independent packed CJS/ESM/types/bin consumers and bilingual site/browser/accessibility checks. The release candidate is subject to fresh CI and `release:preflight`; this note alone does not claim they passed.
+- Private SSH/Atlas environments remain operator-managed supplemental checks. OIDC readiness does not prove npm-side trusted-publisher configuration; npm validates it during the actual publish.

package/dist/cjs/cli/data-task.cjs

@@ -31,7 +31,7 @@ var import_node_url = require("node:url");
 // package.json
 var package_default = {
   name: "monsqlize",
-  version: "3.3.0",
+  version: "3.3.2",
   description: "TypeScript production data runtime layer for MongoDB today, with cache, transactions, pools, models, sync, and observability",
   type: "commonjs",
   main: "./dist/cjs/index.cjs",
@@ -52,6 +52,8 @@ var package_default = {
     "./package.json": "./package.json"
   },
   files: [
+    "changelogs/v3.3.2.md",
+    "changelogs/v3.3.1.md",
     "changelogs/v3.3.0.md",
     "changelogs/v3.2.0.md",
     "changelogs/v3.1.14.md",
@@ -142,8 +144,8 @@ var package_default = {
     "check:sizes:strict": "node scripts/check-file-sizes.cjs --strict",
     build: "node scripts/build-p1.cjs",
     "build:tests": "node scripts/compile-tests.cjs",
-    lint: "eslint . --ignore-pattern .generated/** --ignore-pattern dist/** --ignore-pattern .devcodex/**",
-    "lint:fix": "eslint . --fix --ignore-pattern .generated/** --ignore-pattern dist/** --ignore-pattern .devcodex/**",
+    lint: "eslint .",
+    "lint:fix": "eslint . --fix",
     "test:runtime": "npm run build && npm run build:tests && node --test .generated/test-dist/test/smoke/root-cjs.test.js .generated/test-dist/test/smoke/root-esm.test.js .generated/test-dist/test/smoke/pack-artifacts.test.js",
     "test:compatibility": "npm run build && npm run build:tests && node --test .generated/test-dist/test/compatibility/exports/exports.test.js .generated/test-dist/test/compatibility/matrix.test.js",
     "probe:server-matrix": "node scripts/validation/probe-memory-server-matrix.cjs",
@@ -152,7 +154,7 @@ var package_default = {
     "test:examples": "npm run build && tsc -p tsconfig.examples.json && node scripts/run-examples.cjs",
     "test:performance": "npm run build && npm run build:tests && node .generated/test-dist/test/performance/baselines/function-cache.benchmark.js",
     "test:unit": "npm run build && npm run build:tests && node test/run-tests.cjs unit",
-    "test:integration": "npm run build && npm run build:tests && node --test --test-concurrency=1 .generated/test-dist/test/integration/cache/cache.test.js .generated/test-dist/test/integration/cache/cache-behavior.test.js .generated/test-dist/test/integration/mongodb/connect.test.js .generated/test-dist/test/integration/mongodb/queries.test.js .generated/test-dist/test/integration/mongodb/management.test.js .generated/test-dist/test/integration/mongodb/writes-batch.test.js .generated/test-dist/test/integration/mongodb/find.test.js .generated/test-dist/test/integration/mongodb/find-one.test.js .generated/test-dist/test/integration/mongodb/find-page.test.js .generated/test-dist/test/integration/mongodb/aggregate.test.js .generated/test-dist/test/integration/mongodb/chaining.test.js .generated/test-dist/test/integration/mongodb/insert.test.js .generated/test-dist/test/integration/mongodb/update.test.js .generated/test-dist/test/integration/mongodb/delete.test.js .generated/test-dist/test/integration/mongodb/update-pipeline.test.js .generated/test-dist/test/integration/model/model-features.test.js .generated/test-dist/test/integration/transaction/transaction.test.js .generated/test-dist/test/integration/pool/pool.test.js .generated/test-dist/test/integration/pool/pool-behavior.test.js .generated/test-dist/test/integration/watch/watch-native.test.js .generated/test-dist/test/integration/runtime/runtime-core-regression.test.js .generated/test-dist/test/integration/sync/sync.test.js .generated/test-dist/test/integration/slow-query-log/slow-query-log.test.js .generated/test-dist/test/integration/model/model-crud-extended.test.js .generated/test-dist/test/integration/mongodb/management-complete.test.js .generated/test-dist/test/integration/runtime/runtime-methods-extended.test.js .generated/test-dist/test/integration/mongodb/find-page-advanced.test.js",
+    "test:integration": "npm run build && npm run build:tests && node --test --test-concurrency=1 .generated/test-dist/test/integration/cache/cache.test.js .generated/test-dist/test/integration/cache/cache-behavior.test.js .generated/test-dist/test/integration/mongodb/connect.test.js .generated/test-dist/test/integration/mongodb/queries.test.js .generated/test-dist/test/integration/mongodb/management.test.js .generated/test-dist/test/integration/mongodb/writes-batch.test.js .generated/test-dist/test/integration/mongodb/find.test.js .generated/test-dist/test/integration/mongodb/find-one.test.js .generated/test-dist/test/integration/mongodb/find-page.test.js .generated/test-dist/test/integration/mongodb/aggregate.test.js .generated/test-dist/test/integration/mongodb/chaining.test.js .generated/test-dist/test/integration/mongodb/insert.test.js .generated/test-dist/test/integration/mongodb/update.test.js .generated/test-dist/test/integration/mongodb/delete.test.js .generated/test-dist/test/integration/mongodb/update-pipeline.test.js .generated/test-dist/test/integration/model/model-features.test.js .generated/test-dist/test/integration/transaction/transaction.test.js .generated/test-dist/test/integration/pool/pool.test.js .generated/test-dist/test/integration/pool/pool-behavior.test.js .generated/test-dist/test/integration/watch/watch-native.test.js .generated/test-dist/test/integration/runtime/runtime-core-regression.test.js .generated/test-dist/test/integration/runtime/review-regressions.test.js .generated/test-dist/test/integration/sync/sync.test.js .generated/test-dist/test/integration/slow-query-log/slow-query-log.test.js .generated/test-dist/test/integration/model/model-crud-extended.test.js .generated/test-dist/test/integration/mongodb/management-complete.test.js .generated/test-dist/test/integration/runtime/runtime-methods-extended.test.js .generated/test-dist/test/integration/mongodb/find-page-advanced.test.js .generated/test-dist/test/integration/mongodb/review-repair-regressions.test.js .generated/test-dist/test/integration/model/review-model-regressions.test.js .generated/test-dist/test/integration/slow-query-log/review-storage-regressions.test.js",
     "test:data-tasks:integration": "npm run build && npm run build:tests && node test/run-tests.cjs data-tasks-integration",
     "test:data-task-cli": "npm run build && npm run build:tests && node test/run-tests.cjs data-task-cli",
     "test:pack-install": "npm run build && node scripts/pack-install-smoke.cjs",
@@ -196,7 +198,7 @@ var package_default = {
     ssh2: "1.17.0"
   },
   overrides: {
-    "fast-uri": "3.1.5",
+    "fast-uri": "^3.1.8",
     "minimatch@3.1.5": {
       "brace-expansion": "1.1.18"
     },