cosmosdb-server

Changes We are testing with v3.17.3 instead of v3.10.x. The reason for that is that we need v3.15.x to support Patch operations, and since we are already updating the library, I have bumped it to the latest 3.X version, which is maintenance mode (they are already in the version v4.5+). Bumping to version v4.X should be another PR as it is a breaking change and more risky. In this PR I am only interested in adding support for the Patch operations. Another change is supporting Node 20 and 22 in the test matrix. We are also removing support for Node 14, 16 and 18, as they have reached their EOL and the new version from does not support that. Removing this support means it is a BREAKING CHANGE. The default NodeJS version has been moved from Node 14 to Node 20. What is Patch updates? Patch (Partial) updates allow us to only modify the fields that have changed from a CosmosDB document. Otherwise, the default behavior is to delete and create the Document again, which means the RU consumption increases in proportion to the Document size and we introduce more latency. Testing I have added integration tests to support the all patch operations, even if in the end we will only use three operations: , , . The main reason is that the main tests from azure SDK try all patch operations, and we want to pass them. There is also an additional test to verify that the condition works, if used. Also, I had to update the gitsubmodule used for testing to the latest one, due to errors and issues with all the previous versions.