@visa/cli 5.0.0-rc.366 → 5.0.0-rc.368
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 +10 -0
- package/dist/cli.js +246 -244
- package/dist/mcp-server/index.js +200 -198
- package/dist/merchant-ucp-mcp/index.js +6 -6
- package/native/bin/win32-arm64/visa-runtime-signer.exe +0 -0
- package/native/bin/win32-x64/visa-runtime-signer.exe +0 -0
- package/package.json +1 -1
- package/server.json +2 -2
package/README.md
CHANGED
|
@@ -403,6 +403,16 @@ service's paid route with `discover { "query": "<what you want>" }`.
|
|
|
403
403
|
The ceremony timed out — run `visa connect` again. Do not look for a resume
|
|
404
404
|
command; the retired setup doors are removed, and `connect` is idempotent.
|
|
405
405
|
|
|
406
|
+
**Enrollment or TAP signing returns `update_required` / HTTP 426**
|
|
407
|
+
|
|
408
|
+
The server requires a newer CLI. The error names the running and minimum
|
|
409
|
+
compatible versions. Run `npm install -g @visa/cli@rc`, then run `visa connect`
|
|
410
|
+
again. For MCP, restart the MCP server so it loads the updated binary before
|
|
411
|
+
calling `agent_enroll` again. Repeating `connect --restart` alone cannot fix a
|
|
412
|
+
version refusal. A TAP-only refusal does not undo completed wallet/card setup;
|
|
413
|
+
the result carries `tapDiagnostic.code: "update_required"` and the upgrade remedy,
|
|
414
|
+
even while device approval is still pending.
|
|
415
|
+
|
|
406
416
|
**`session` is false with a certificate error, but the website works**
|
|
407
417
|
Codes like `UNABLE_TO_GET_ISSUER_CERT_LOCALLY`, `SELF_SIGNED_CERT_IN_CHAIN` or
|
|
408
418
|
`DEPTH_ZERO_SELF_SIGNED_CERT` mean this machine would not trust the connection,
|