@lossless.org/nosqldb 10.4.0 → 10.5.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lossless.org/nosqldb",
-  "version": "10.4.0",
+  "version": "10.5.1",
   "private": false,
   "description": "A MongoDB-compatible embedded database server with wire protocol support, backed by a high-performance Rust engine.",
   "exports": {
@@ -14,12 +14,12 @@
   "devDependencies": {
     "@api.global/typedserver": "^8.4.6",
     "@design.estate/dees-element": "^2.2.4",
-    "@git.zone/tsbuild": "^4.5.0",
-    "@git.zone/tsbundle": "^2.13.0",
+    "@git.zone/tsbuild": "^5.0.0",
+    "@git.zone/tsbundle": "^2.15.0",
     "@git.zone/tsrust": "^1.13.2",
-    "@git.zone/tstest": "^6.1.1",
+    "@git.zone/tstest": "^6.2.0",
     "@lossless.org/client": "0.1.1",
-    "@types/node": "26.5.1",
+    "@types/node": "26.6.1",
     "mongodb": "^7.5.0"
   },
   "dependencies": {

package/readme.md

@@ -559,6 +559,17 @@ see the transaction snapshot plus its staged changes. Commit validates conflicts
 and publishes atomically; abort discards staged changes. Write conflicts report
 `WriteConflict` (112) with `TransientTransactionError`.
 
+A staged write conflicts when it touches a document `_id` or a unique index key
+that another transaction or statement wrote after this transaction's snapshot:
+for example two transactions that both read a claim as absent and then insert
+it under the same `_id`, or under distinct `_id`s with the same unique key.
+Statements validate against the snapshot, so such a collision is reported when
+the loser commits; nothing of the losing transaction is published. The driver's
+`withTransaction` retries the transient error, and the retry observes the
+winner. A key already visible in the transaction's snapshot is not a conflict:
+inserting it fails the statement with `DuplicateKey` (11000), as outside a
+transaction.
+
 Commit/abort outcomes and successful retryable statement results survive file
 storage restart. Duplicate commits replay their outcome; abort after commit
 reports `TransactionCommitted` (256), commit after abort reports
@@ -1325,6 +1336,12 @@ await collection.findOneAndReplace({ _id: id }, { name: 'Replaced' }, { returnDo
 { $currentDate: { lastModified: true } }
 ```
 
+Aggregation-pipeline updates are supported wherever the MongoDB driver accepts
+them (`updateOne`, `updateMany`, `findOneAndUpdate`, and upserts): the update
+may be an array of `$addFields`, `$set`, `$project`, `$unset`, `$replaceRoot`
+or `$replaceWith` stages, and any other stage is refused by name. The pipeline
+must produce exactly one document and cannot change `_id`.
+
 ### Aggregation Pipeline
 
 ```typescript
@@ -1339,6 +1356,12 @@ const results = await collection.aggregate([
 
 **Supported stages:** `$match`, `$project`, `$group`, `$sort`, `$limit`, `$skip`, `$unwind`, `$lookup`, `$addFields`, `$count`, `$facet`, `$replaceRoot`, `$set`, `$unionWith`, `$out`, `$merge`
 
+**Supported expression operators:** `$eq`, `$and`, `$literal`, `$map`,
+`$objectToArray`, `$setEquals`, plus `$field` paths, `$$variable` references
+including `$$ROOT`, and documents or arrays of those. Every other operator is
+refused by name with `TypeMismatch` (code 14) before any document is read; the
+engine never treats an operator it cannot execute as a literal value.
+
 `$lookup` supports the equality form and a bounded correlated pipeline form with
 `let`, an optional `$match` using `$expr`/`$and`/`$eq`, and an optional following
 `$limit`. Correlated string equality predicates can use a full-key or subset
@@ -1358,6 +1381,19 @@ is what lets `countDocuments(filter)` run against collections larger than it.
 
 **Group accumulators:** `$sum`, `$avg`, `$min`, `$max`, `$first`, `$last`, `$push`, `$addToSet`, `$count`
 
+`$group._id` accepts a literal (`null`, a number, a string), a `$field`
+reference, or a document of expressions: `{ _id: { owner: '$owner', repo:
+'$repo' } }` groups by the evaluated pair, one group per distinct composite
+key. Inside a composite `_id`, a member whose field is absent evaluates to
+`null` and stays part of the key, where MongoDB omits the member instead.
+Accumulator operands accept the same expression forms. A field reference
+resolves per document, and a missing field is not a value: `$sum`, `$avg`,
+`$min`, `$max`, `$push` and `$addToSet` skip it, while `$first` and `$last`
+record `null` for it. Every field beside `_id` must hold an accumulator
+document naming exactly one accumulator, such as `{ $sum: 1 }`, and an operator
+outside the two lists above is refused with `TypeMismatch` (code 14) when the
+stage is parsed.
+
 ### Indexes
 
 ```typescript
@@ -1430,9 +1466,11 @@ Without a limit, exact counts continue to EOF. Hints, deadlines and empty-result
 shapes remain supported; signed BSON count overflow and resource exhaustion
 reject explicitly. Exact counts never substitute estimates, and transaction
 counts retain the snapshot admission limits described below.
-Grouping accumulates one group at a time after an external sort; constant-key
-groups stream directly. Group accumulator semantics follow the documented local
-expression surface; this does not add the complete MongoDB aggregation language.
+Grouping accumulates one group at a time after an external sort over the group
+key; only keys with no field reference and no operator stream directly into a
+single group. Composite document keys sort and group like any other key. Group
+key and accumulator semantics follow the supported expression operators listed
+above; this does not add the complete MongoDB aggregation language.
 Unwind retains one input while expanding arrays across batches. Lookup scans
 bounded foreign pages or indexed candidates, then assembles one byte-bounded
 result document. Unindexed joins can still require repeated foreign scans.

package/ts/00_commitinfo_data.ts

@@ -3,6 +3,6 @@
  */
 export const commitinfo = {
   name: '@lossless.org/nosqldb',
-  version: '10.4.0',
+  version: '10.5.1',
   description: 'A MongoDB-compatible embedded database server with wire protocol support, backed by a high-performance Rust engine.'
 }