@muggleai/works 4.8.2 → 4.8.3

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.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "muggle",
3
3
  "description": "Run real-browser end-to-end (E2E) acceptance tests on your web app from any AI coding agent. Generate test scripts from plain English, replay them on localhost, capture screenshots, and validate user flows like signup, checkout, and dashboards. Works across Claude Code, Cursor, Codex, and Windsurf.",
4
- "version": "4.8.2",
4
+ "version": "4.8.3",
5
5
  "author": {
6
6
  "name": "Muggle AI",
7
7
  "email": "support@muggle-ai.com"
@@ -2,7 +2,7 @@
2
2
  "name": "muggle",
3
3
  "displayName": "Muggle AI",
4
4
  "description": "Ship quality products with AI-powered end-to-end (E2E) acceptance testing that validates your web app like a real user — from Claude Code and Cursor to PR.",
5
- "version": "4.8.2",
5
+ "version": "4.8.3",
6
6
  "author": {
7
7
  "name": "Muggle AI",
8
8
  "email": "support@muggle-ai.com"
@@ -5,17 +5,29 @@ description: Update Muggle AI to latest version. Use when user types muggle upgr
5
5
 
6
6
  # Muggle Upgrade
7
7
 
8
- Update all Muggle AI components to the latest published version.
8
+ Update all Muggle AI components to the latest published version. This means **both** the `@muggleai/works` CLI on npm **and** the Electron runner the CLI manages.
9
9
 
10
10
  ## Steps
11
11
 
12
12
  1. Run `/muggle:muggle-status` checks to capture current versions.
13
- 2. Run `muggle upgrade` to check GitHub releases for the latest electron-app version and download it.
14
- 3. Report the upgrade results:
15
- - Previous version vs new version for each component.
16
- - Whether the upgrade succeeded or failed.
17
- 4. Run `/muggle:muggle-status` again to confirm everything is healthy after upgrade.
13
+
14
+ 2. Capture CLI versions:
15
+ - Installed CLI: `muggle --version`
16
+ - Latest on npm: `npm view @muggleai/works version`
17
+ - Detect install location: `npm ls -g @muggleai/works --depth=0` (falls back to `pnpm ls -g @muggleai/works` if not found)
18
+
19
+ 3. **If installed CLI < latest on npm**, upgrade the CLI itself before touching Electron:
20
+ - npm global install: `npm install -g @muggleai/works@latest`
21
+ - pnpm global install: `pnpm add -g @muggleai/works@latest`
22
+ - If neither is detected, report the situation and ask the user how the CLI was installed before proceeding.
23
+
24
+ 4. Run `muggle upgrade` to pull the Electron runner version that the (now-latest) CLI expects.
25
+ - Note: `muggle upgrade` only manages the Electron runner — it does NOT upgrade the CLI npm package. That is why step 3 must run first.
26
+
27
+ 5. Run `/muggle:muggle-status` again to confirm everything is healthy after upgrade.
18
28
 
19
29
  ## Output
20
30
 
21
- Show a before/after version comparison. If the upgrade fails at any step, report the error and suggest running `/muggle:muggle-repair`.
31
+ Show a before/after table for **CLI**, **Electron runner**, **MCP server**, and **Auth**. Call out any version that did not change so the user understands what shipped vs what was already current.
32
+
33
+ If the upgrade fails at any step, report the error and suggest running `/muggle:muggle-repair`.
@@ -1,7 +1,7 @@
1
1
  {
2
- "release": "4.8.2",
3
- "buildId": "run-21-1",
4
- "commitSha": "a654d42a8f3fccd94a876740a4d564807e16cd9a",
5
- "buildTime": "2026-04-14T22:44:16Z",
2
+ "release": "4.8.3",
3
+ "buildId": "run-23-1",
4
+ "commitSha": "db2ab1ae29f982b0a12db6dbd2a334cc8016f016",
5
+ "buildTime": "2026-04-14T23:24:16Z",
6
6
  "serviceName": "muggle-ai-works-mcp"
7
7
  }
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@muggleai/works",
3
3
  "mcpName": "io.github.multiplex-ai/muggle",
4
- "version": "4.8.2",
4
+ "version": "4.8.3",
5
5
  "description": "Ship quality products with AI-powered E2E acceptance testing that validates your web app like a real user — from Claude Code and Cursor to PR.",
6
6
  "type": "module",
7
7
  "main": "dist/index.js",
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "muggle",
3
3
  "description": "Run real-browser end-to-end (E2E) acceptance tests on your web app from any AI coding agent. Generate test scripts from plain English, replay them on localhost, capture screenshots, and validate user flows like signup, checkout, and dashboards. Works across Claude Code, Cursor, Codex, and Windsurf.",
4
- "version": "4.8.2",
4
+ "version": "4.8.3",
5
5
  "author": {
6
6
  "name": "Muggle AI",
7
7
  "email": "support@muggle-ai.com"
@@ -2,7 +2,7 @@
2
2
  "name": "muggle",
3
3
  "displayName": "Muggle AI",
4
4
  "description": "Ship quality products with AI-powered end-to-end (E2E) acceptance testing that validates your web app like a real user — from Claude Code and Cursor to PR.",
5
- "version": "4.8.2",
5
+ "version": "4.8.3",
6
6
  "author": {
7
7
  "name": "Muggle AI",
8
8
  "email": "support@muggle-ai.com"
@@ -5,17 +5,29 @@ description: Update Muggle AI to latest version. Use when user types muggle upgr
5
5
 
6
6
  # Muggle Upgrade
7
7
 
8
- Update all Muggle AI components to the latest published version.
8
+ Update all Muggle AI components to the latest published version. This means **both** the `@muggleai/works` CLI on npm **and** the Electron runner the CLI manages.
9
9
 
10
10
  ## Steps
11
11
 
12
12
  1. Run `/muggle:muggle-status` checks to capture current versions.
13
- 2. Run `muggle upgrade` to check GitHub releases for the latest electron-app version and download it.
14
- 3. Report the upgrade results:
15
- - Previous version vs new version for each component.
16
- - Whether the upgrade succeeded or failed.
17
- 4. Run `/muggle:muggle-status` again to confirm everything is healthy after upgrade.
13
+
14
+ 2. Capture CLI versions:
15
+ - Installed CLI: `muggle --version`
16
+ - Latest on npm: `npm view @muggleai/works version`
17
+ - Detect install location: `npm ls -g @muggleai/works --depth=0` (falls back to `pnpm ls -g @muggleai/works` if not found)
18
+
19
+ 3. **If installed CLI < latest on npm**, upgrade the CLI itself before touching Electron:
20
+ - npm global install: `npm install -g @muggleai/works@latest`
21
+ - pnpm global install: `pnpm add -g @muggleai/works@latest`
22
+ - If neither is detected, report the situation and ask the user how the CLI was installed before proceeding.
23
+
24
+ 4. Run `muggle upgrade` to pull the Electron runner version that the (now-latest) CLI expects.
25
+ - Note: `muggle upgrade` only manages the Electron runner — it does NOT upgrade the CLI npm package. That is why step 3 must run first.
26
+
27
+ 5. Run `/muggle:muggle-status` again to confirm everything is healthy after upgrade.
18
28
 
19
29
  ## Output
20
30
 
21
- Show a before/after version comparison. If the upgrade fails at any step, report the error and suggest running `/muggle:muggle-repair`.
31
+ Show a before/after table for **CLI**, **Electron runner**, **MCP server**, and **Auth**. Call out any version that did not change so the user understands what shipped vs what was already current.
32
+
33
+ If the upgrade fails at any step, report the error and suggest running `/muggle:muggle-repair`.