{"slug": "mendapi-0-5-5-the-one-bug-we-shipped-on-purpose-now-fixed", "title": "Mendapi 0.5.5: the one bug we shipped on purpose, now fixed", "summary": "Mendapi 0.5.5 fixes a bug where 'mendapi scan -h' ran a scan instead of printing help, a known issue shipped in 0.5.4. The fix normalizes '-h' to '--help' for all nine subcommands, and the regression gate now asserts on all subcommands with a negative control. The MCP registry entry has also been refreshed with an icon set and website URL.", "body_md": "The 0.5.4 release notes carried an unusual section: **Known issue shipped with 0.5.4**. We had spent that whole release fixing the first minute of using the CLI — twelve corrections to help text, exit codes, path handling, and MCP behaviour — and in the middle of it we found one more that did not make the cut.\n\n`mendapi scan -h`\n\ndid not print help. It ran a scan.\n\nEvery other subcommand normalized `-h`\n\nto `--help`\n\nbefore dispatching. `scan`\n\ndid not, so the short flag fell through to the scanner, which happily ignored an unrecognized argument and started working. Nobody loses data over this. But it is exactly the kind of thing that makes a first-time user close the terminal, and we had just shipped a release about first impressions.\n\nWe wrote it down rather than quietly patching over it, because a tool whose entire premise is *upstream changes should be visible before they surprise you* does not get to hide its own.\n\nOne change. `-h`\n\nis normalized to `--help`\n\nbefore any subcommand spawns, so all nine subcommands behave identically:\n\n``` bash\n$ npx mendapi@0.5.5 scan -h\n\nUsage: mendapi scan\n  --repo <path>\n  --provider <name>\n  --change-id <id>\n  --out <file.json>\n  --json --quiet\n  --include-prereleases\n```\n\nThe regression gate that covers this now asserts on all nine subcommands, plus a negative control that fails if the assertion ever becomes vacuously true. That second part matters more than the fix: a test that passes because it stopped testing anything is worse than no test.\n\nThe MCP registry entry has been refreshed. `com.mendapi/mendapi`\n\nnow carries an icon set and a website URL alongside the package metadata, so clients that render a server picker have something to render.\n\nNothing else changed. `scan`\n\n, `fix`\n\n, `deps`\n\n, `review`\n\n, and `pr`\n\nstill run entirely on your machine. No network primitives exist in those files at all, and the build fails if any appear.\n\n```\nnpx mendapi@latest scan\n```\n\nOr wire it into an agent:\n\n```\nclaude mcp add mendapi \\\n  -- npx mendapi mcp\n```\n\nRequires Node.js 22.13 or newer. Zero npm dependencies.", "url": "https://wpnews.pro/news/mendapi-0-5-5-the-one-bug-we-shipped-on-purpose-now-fixed", "canonical_source": "https://dev.to/mendapi/mendapi-055-the-one-bug-we-shipped-on-purpose-now-fixed-2ge4", "published_at": "2026-08-04 03:13:56+00:00", "updated_at": "2026-08-04 03:52:14.422920+00:00", "lang": "en", "topics": ["developer-tools"], "entities": ["Mendapi"], "alternates": {"html": "https://wpnews.pro/news/mendapi-0-5-5-the-one-bug-we-shipped-on-purpose-now-fixed", "markdown": "https://wpnews.pro/news/mendapi-0-5-5-the-one-bug-we-shipped-on-purpose-now-fixed.md", "text": "https://wpnews.pro/news/mendapi-0-5-5-the-one-bug-we-shipped-on-purpose-now-fixed.txt", "jsonld": "https://wpnews.pro/news/mendapi-0-5-5-the-one-bug-we-shipped-on-purpose-now-fixed.jsonld"}}