Keep pinned Axe MCP Server, axe-auth, and Playwright versions in sync across the repo

Open Beginner friendly
#9 2 comments 1 reaction 1 assignee View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
shell
Domain
documentation

Research direction

Start by searching the repository for the pinned versions of axe-mcp-server, @deque/axe-auth, and playwright, then inspect existing AGENTS.md files and the launch script, plugin.json, README, and skill docs. Add repo-wide instructions that distinguish current pins from historical references and require re-checking release-specific guidance when the server pin changes. Done means the instructions cover the acceptance criteria and all current-pin references agree.

Written by the indexing model from the issue text.

Description

The plugin pins exact versions of axe-mcp-server, @deque/axe-auth, and playwright in its launch script, plugin.json, the README, and the skill docs. The plugin directory review requires pinned versions, so they stay. Today the pin appears about 30 times across 7 files with nothing tying them together. A release bump that updates only the files in the diff leaves the rest stale, so users get inconsistent setup instructions.

Some skill docs also say their guidance matches a specific server release. A bump that changes the number without re-checking that guidance makes the docs claim accuracy they no longer have.

Acceptance criteria:

  • AGENTS.md requires re-checking every doc that claims to match a specific server release whenever the server pin changes.
  • AGENTS.md separates current pins, which CI keeps in sync (#13), from historical "introduced in X" references, which must not be bumped.

Refs #8

Dominant language
Shell
Stars
3
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dequelabs/axe-accessibility

All issues in dequelabs/axe-accessibility

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.