@noy-db/test-sealer-conformance 0.7.0-pre.0 → 0.7.0-pre.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -45,7 +45,7 @@ Both obligations are already satisfied by every wired provider, so those tests *
|
|
|
45
45
|
|
|
46
46
|
### ⚠️ `at-azure-keyvault` cannot be tested at all
|
|
47
47
|
|
|
48
|
-
Every other `at-*` provider takes an injection seam — `entry` for the Keychain, `client` for AWS and GCP. `
|
|
48
|
+
Every other `at-*` provider takes an injection seam — `entry` for the Keychain, `client` for AWS and GCP. `AtAzureKeyvaultOptions` takes only `keyId` and `algorithm`, so there is no way to exercise it without a real Key Vault. It is the one provider with **no coverage of either kind**, and closing that needs a production change (add `client?:`), not a test.
|
|
49
49
|
|
|
50
50
|
### Still owed
|
|
51
51
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@noy-db/test-sealer-conformance",
|
|
3
|
-
"version": "0.7.0-pre.
|
|
3
|
+
"version": "0.7.0-pre.2",
|
|
4
4
|
"description": "Parameterized contract tests for noy-db sealing-key providers — the conformance suite every NoydbSealer implementation must pass",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"author": "vLannaAi <vicio@lanna.ai>",
|
|
@@ -33,11 +33,11 @@
|
|
|
33
33
|
},
|
|
34
34
|
"peerDependencies": {
|
|
35
35
|
"vitest": "^3.0.0",
|
|
36
|
-
"@noy-db/hub": "0.7.0-pre.
|
|
36
|
+
"@noy-db/hub": "0.7.0-pre.2"
|
|
37
37
|
},
|
|
38
38
|
"devDependencies": {
|
|
39
39
|
"vitest": "^3.0.0",
|
|
40
|
-
"@noy-db/hub": "0.7.0-pre.
|
|
40
|
+
"@noy-db/hub": "0.7.0-pre.2"
|
|
41
41
|
},
|
|
42
42
|
"keywords": [
|
|
43
43
|
"noy-db",
|