midnight-wallet-cli 0.4.1 → 0.5.1

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/docs/SKILL.md CHANGED
@@ -77,7 +77,7 @@ Use `midnight_contract_*` MCP tools (or `mn contract` CLI). Flow: `compact compi
77
77
 
78
78
  Plain strings, booleans, fractional numbers, and `null` pass through unchanged. No hex-string detection — `"1234"` stays a string.
79
79
 
80
- **Compatibility caveat — runtime version skew.** Contracts compiled with an older `compactc` may fail at deploy/call with a message like `Version mismatch: compiled code expects <X>, runtime is <Y>`. The CLI bundles one specific `@midnight-ntwrk/compact-runtime` version; if the user's contract was compiled against a different one, recompile the contract with a matching `compactc` rather than asking the user to downgrade `mn`. `midnight_contract_inspect` shows the compiled `runtimeVersion` so you can flag the mismatch before attempting deploy.
80
+ **Compatibility caveat — runtime version skew.** Contracts must be compiled with the current Compact toolchain. The CLI bundles `@midnight-ntwrk/compact-runtime` `^0.16.0`, so contracts have to target runtime `0.16.0`. Pre-compiled artifacts built for an older runtime (e.g. `0.15.0`) are rejected at deploy/call with a clear message like `CompactError: Version mismatch: compiled code expects 0.15.0`. The fix is to recompile against the current runtime — run `compact compile` (or `mn dev`, which auto-compiles on save) rather than asking the user to downgrade `mn`. `midnight_contract_inspect` shows the compiled `runtimeVersion` so you can flag the mismatch before attempting deploy.
81
81
 
82
82
  **Stale MCP server.** Every MCP response carries `_serverVersion`. If the user upgraded `midnight-wallet-cli` but `_serverVersion` lags `mn --version`, the MCP client is talking to a long-lived stale process. Tell them to disconnect and re-add the MCP server (a /mcp reconnect alone will not respawn it).
83
83
 
package/package.json CHANGED
@@ -1,9 +1,10 @@
1
1
  {
2
2
  "name": "midnight-wallet-cli",
3
- "version": "0.4.1",
3
+ "version": "0.5.1",
4
4
  "type": "module",
5
5
  "description": "Git-style CLI wallet for the Midnight blockchain",
6
6
  "license": "Apache-2.0",
7
+ "author": "Norman Lopez (https://github.com/nel349)",
7
8
  "homepage": "https://github.com/nel349/midnight-wallet-cli#readme",
8
9
  "repository": {
9
10
  "type": "git",
@@ -34,12 +35,18 @@
34
35
  },
35
36
  "files": [
36
37
  "dist",
37
- "docs/SKILL.md"
38
+ "docs/SKILL.md",
39
+ "NOTICE"
38
40
  ],
41
+ "engines": {
42
+ "node": ">=20",
43
+ "bun": ">=1.3.0"
44
+ },
39
45
  "scripts": {
40
46
  "wallet": "tsx src/wallet.ts",
41
47
  "build": "bun build src/wallet.ts --outfile dist/wallet.js --target node --format esm --packages external --minify --banner \"#!/usr/bin/env node\" && bun build src/mcp-server.ts --outfile dist/mcp-server.js --target node --format esm --packages external --minify --banner \"#!/usr/bin/env node\"",
42
48
  "mcp": "tsx src/mcp-server.ts",
49
+ "link": "bun link",
43
50
  "prepublishOnly": "npm run build && npm run test",
44
51
  "test": "vitest run",
45
52
  "test:watch": "vitest",