Keep pinned Axe MCP Server, axe-auth, and Playwright versions in sync across the repo
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.mdrequires re-checking every doc that claims to match a specific server release whenever the server pin changes. -
AGENTS.mdseparates 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dequelabs/axe-accessibility
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 4/5 3-5 days Newbie friendliness 57/100
-
Difficulty 3/5 1-2 days Newbie friendliness 66/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
All issues in dequelabs/axe-accessibility
Similar issues
-
bug report-to-upstream
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
flatpark/flatpark#1424 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
[bug] Docker Compose version check in auto-install.sh fails on non-Debian systems (dpkg not found)Possibly taken @shaneintentionboi06 claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
openwisp/docker-openwisp#771 ·
Maintainers usually reply within 1 day
-
needs-you
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
catalystneuro/encore#860 ·
Maintainers usually reply within 1 day
-
Update crush to 0.102.0Possibly taken @zen0bit claimed this today. Openpackage-update
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
oSoWoSo/oco#1251 · 1 comment ·
Maintainers usually reply within 1 day