@icoretech/warden-mcp 0.1.14 → 0.1.15
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 +9 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -65,6 +65,10 @@ can change login and unlock behavior in ways that break automation, so `bw`
|
|
|
65
65
|
upgrades should be smoke-tested against real Vaultwarden and Bitwarden flows
|
|
66
66
|
before bumping the bundled version.
|
|
67
67
|
|
|
68
|
+
This repository's compose smoke now exercises both username/password auth and
|
|
69
|
+
user API-key auth against a real local Vaultwarden so `@bitwarden/cli` bumps do
|
|
70
|
+
not rely on unit coverage alone.
|
|
71
|
+
|
|
68
72
|
## Install And Run
|
|
69
73
|
|
|
70
74
|
### Choose a transport
|
|
@@ -452,6 +456,11 @@ Run integration tests:
|
|
|
452
456
|
make test
|
|
453
457
|
```
|
|
454
458
|
|
|
459
|
+
`make test` now runs both compose-backed auth paths:
|
|
460
|
+
|
|
461
|
+
- user/password login from `.env.test`
|
|
462
|
+
- api-key login from `tmp/vaultwarden-bootstrap/apikey.env`, generated by the bootstrap step and kept out of git via `tmp/`
|
|
463
|
+
|
|
455
464
|
Run session flood regression locally (guardrail sanity):
|
|
456
465
|
|
|
457
466
|
```bash
|