Skip to content

qmax-mcp 0.9.2

Latest

Choose a tag to compare

@github-actions github-actions released this 13 Oct 10:26
· 7 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.9.2
22f3d16

The final release of @qualitymax/qmax-mcp. Its checks now ship in 9lives:
9l scan and 9l inspect from a shell, and 9l mcp for coding agents
(9lives-runner, from v0.4.0).
This package stays installable but receives no further fixes; new work and the
issues that were open here moved to 9lives-runner. Results are comparable with
0.9.1, except for the inspect changes listed under Fixed.

Changed

  • The README, package description, MCP Registry entry and Smithery metadata
    name the move to 9lives, and the website links point to 9lives.run instead of
    qmax.run, which no longer hosts this project. Connected agents get one short
    instruction naming 9l mcp, for use only when a person asks about updates, a
    bug or a missing feature.

Fixed

  • A missing browser now fails with the command that installs the right build:
    npx -y playwright@<version> install chromium, using the Playwright version
    qmax-mcp resolved. It no longer shows Playwright's banner. The banner's
    npx playwright install, run in a project, installs browsers for that
    project's own Playwright version, which is the right build only by
    coincidence (#119).
  • A network refusal now says which rule applied. A loopback URL without consent
    is pointed at allowPrivateNetwork / --allow-private-network. With consent,
    any host other than localhost, 127.0.0.0/8 or ::1 written in the URL
    (a Docker Compose service name, say) is told that only those qualify and to
    use the host-published port. The text depends only on the caller's input,
    never on DNS results, so it reveals nothing about the internal network
    (#119).
  • inspect no longer presents a name attribute as if it were an accessible
    name. The Markdown report quotes a control's name only when it is an
    accessible name; otherwise the control reads checkbox [name=rememberMe] (no accessible name). Each interactive entry gains accessibleName: the
    browser's computed name, the same one its accessibility tree node carries.
    Locator names follow the same rules. A <select>'s option text is no longer
    taken as its name, and an <input type="submit"> is named by its value. A
    control found by a test id or an id but with no accessible name keeps its 🟢
    stable verdict and now carries an "easy to locate, not accessible" caveat. For
    a form field, the caveat names the matching scan finding. Before this,
    inspect rated an unlabelled checkbox as named and stable, while scan
    flagged the same control as a high-severity missing label (#133).

Repository, not shipped in the package

  • One run of the release workflow now publishes npm, then the MCP Registry, then
    the GitHub Release. Each job runs only after the one before it succeeded. The
    GitHub Release notes are generated from the version's CHANGELOG entry by
    scripts/release-notes.cjs. 0.9.1 needed two separate dispatches and a
    GitHub Release created by hand.
  • The Publish to MCP Registry liveness check reads the server's latest version
    directly and retries. On 0.9.1 the search endpoint it used returned a 504
    after the publish had succeeded, failing the run. A re-run for a version the
    registry already has now skips the publish and only confirms the entry, and
    the workflow waits for npm to serve the version before publishing.

Install

npx -y @qualitymax/qmax-mcp@0.9.2

Published with npm provenance from tag v0.9.2, commit 22f3d16.

Full details: CHANGELOG.md