Cut a tag of the current main branch for the Pa11y v7.0 update?

[maggiewachs]

The latest tagged version of Pa11y CI (3.1.0) runs on an older version of axe-core that includes several deprecated rules, v4.2.1: https://github.com/dequelabs/axe-core/blob/v4.2.1/doc/rule-descriptions.md

I see there's a PR for the next major release that includes Pa11y 7, which uses axe-core v4.8.2 (#232), but it's in a holding pattern.

Is there any way to tag the current main branch so we can have Pa11y 7 sooner, and eliminate the deprecated axe rules? 🤓

[jamesobrooks]

I agree that it would be nice to be able to take advantage of the updates. Would it include breaking changes so there's no right way to release without going to 4.0.0?

[aarongoldenthal]

I'm not sure what the future holds for it long term, but I started publishing my fork at https://www.npmjs.com/package/@aarongoldenthal/pa11y-ci if it helps anyone (and it uses a similar pa11y fork). It's been focused on dependency/security updates and break-fixes at this point, and was really started as a stop-gap until pa11y/pa11y-ci updates were back to a regular cadence, although it's unclear what that plan is.

It is a v4, partly because of the pa11y/puppeteer updates with breaking changes (through pa11y v8 and beyond), and partly because I changed the pa11y dependency to my fork and that seemed worthy of attention. The migration guide there is up to date and has more info.