@skyramp/mcp 0.5.0-rc.3 → 0.5.0-rc.4
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@skyramp/mcp",
|
|
3
|
-
"version": "0.5.0-rc.
|
|
3
|
+
"version": "0.5.0-rc.4",
|
|
4
4
|
"main": "build/index.js",
|
|
5
5
|
"exports": {
|
|
6
6
|
".": "./build/index.js",
|
|
@@ -79,7 +79,7 @@
|
|
|
79
79
|
"picomatch": "^4.0.5",
|
|
80
80
|
"playwright": "file:vendor/skyramp-playwright-1.58.2-skyramp.8.14.14.tgz",
|
|
81
81
|
"semver": "^7.8.5",
|
|
82
|
-
"simple-git": "^
|
|
82
|
+
"simple-git": "^4.0.1",
|
|
83
83
|
"smol-toml": "^1.8.0",
|
|
84
84
|
"ts-is-record": "^3.0.5",
|
|
85
85
|
"typescript": "^5.8.3",
|
|
@@ -48,7 +48,9 @@ With the SUT healthy, create `.skyramp/workspace.yml`, never by hand: one `skyra
|
|
|
48
48
|
End with one JSON line:
|
|
49
49
|
|
|
50
50
|
```json
|
|
51
|
-
{"status": "ready", "components": [{"name": "api", "repository": "acme/api", "healthy": true}], "suites": [{"framework": "vitest", "file": "api/src/a.test.ts", "result": "fail"}], "inputsUsed": ["deploy/compose.yml"], "inputsNotUsed": [{"input": "ci.yml", "reason": "only lints"}], "blockers": []}
|
|
51
|
+
{"status": "ready", "components": [{"name": "api", "repository": "acme/api", "healthy": true, "credentials": ["STRIPE_API_KEY"]}], "suites": [{"framework": "vitest", "file": "api/src/a.test.ts", "result": "fail"}], "inputsUsed": ["deploy/compose.yml"], "inputsNotUsed": [{"input": "ci.yml", "reason": "only lints"}], "blockers": []}
|
|
52
52
|
```
|
|
53
53
|
|
|
54
|
+
A component's `credentials` name each of the Target's credentials its recipe uses: a sign-in (a test user, password or token) or an API key. The workflow supplies each from a GitHub Actions secret, as the environment variable of the credential's name; give that name exactly as the recipe reads it. Names only; leave out secrets the recipe generates.
|
|
55
|
+
|
|
54
56
|
`ready` only if every component passed; otherwise `blocked`, with at least one blocker. A suite left at `error` gets a blocker too. Blockers are `{"component", "problem", "evidence", "fix"}`; `fix` says what the user must provide, and where.
|
|
@@ -52,4 +52,5 @@ Say exactly what the user must add, and where:
|
|
|
52
52
|
- `start`: `Already deployed at <address>` (source `notes`)
|
|
53
53
|
- `wait`: the ready check, such as `GET /health → 200` (source `notes`, or `testbot` if you found it)
|
|
54
54
|
- `run`: the version, such as `GET /version → e014ac7` (source `testbot`), when one shows
|
|
55
|
+
- In each deployed part's `credentials`, name the credential it signs in with, such as `QA_TEST_USER`.
|
|
55
56
|
- In `inputsUsedHow`, say what each note led to, such as "Set as the ready check" or "Signed in with QA_TEST_USER".
|