Skip to content

chore(deps-dev): bump pa11y-ci from 3.1.0 to 4.1.1 - #3

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/pa11y-ci-4.1.1
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/pa11y-ci-4.1.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 17, 2026 •

Copy link
Copy Markdown

Bumps pa11y-ci from 3.1.0 to 4.1.1.

Release notes

Sourced from pa11y-ci's releases.

v4.1.1

Pa11y CI 4.1.1 updates the lodash dependency to ~4.18.1 to resolve GHSA-f23m-r3pf-42r / CVE-2026-2950.

v4.1.0

What's changed

  • Add support for config files with the .cjs extension
  • Improve documentation for sitemap-exclude
  • Improve npm keywords for better discoverability
  • Replace nyc with c8 for test coverage
  • Replace mockery with quibble for mocking
  • Upgrade dependencies to recent versions matching pa11y's to ensure deduplication works well

New Contributors

Full Changelog: pa11y/pa11y-ci@4.0.1...4.1.0

v4.0.1

Pa11y CI 4.0.1 reintroduces compatibility for node >=20.0.0 <20.18.1.

(At the time of writing, v20.19.4 is the latest version of node 20.)

Pa11y CI 4.0.0 updated the cheerio dependency to 1.1.2. But this causes EBADENGINE warnings when installing if node <20.18.1. We target compatibility with node >20, which after some discussion we think should mean >20.0.0.

Full Changelog: pa11y/pa11y-ci@4.0.0...4.0.1

v4.0.0

Pa11y CI 4.0.0 requires a stable (even-numbered) Node.js version of 20 or above, updates to the latest version of Pa11y (9) and Puppeteer (24), updates several other dependencies, and includes some GitHub actions and documentation cleanup. See the migration guide for details.

Changes

  • Breaking: Upgrade Node.js support: Pa11y CI 4 requires a stable (even-numbered) Node.js version of 20 or above, dropping support for Node 12, 14, 16, 18.
  • Breaking: Upgrade pa11y to 9 (from 6), which updates numerous dependencies, fixes issues with Pa11y CI failing to run on Ubuntu 24.04, and resolves several vulnerabilities and deprecated packages (closing #198, #227, #242, #247).
    • Upgrade puppeteer to 24 (from 9.1), which updates to the current Chrome. This changes Chrome's default headless mode, see the migration guide for details. Also expand the puppeteer dependency compatibility to caret (patch and minor releases) to allow upgrades to a more recent compatible version upon install (which frequently contains Chrome updates and security patches).
    • Upgrade axe-core to 4.10 from 4.2. This includes rule fixes that may change results when using the axe runner. See axe-core releases for complete details.
    • Upgrade semver to 7.7 from 7.3, resolving CVE-2022-25883.
  • Fixed issue with pa11y-ci process hanging if browser passed from config file. (#248)
  • Other dependency upgrades: commander to 14.0, async to 3.2, cheerio to 1.1, and node-fetch to 2.7.
  • GitHub Actions changes: Update workflows for supported Node version, Ubuntu 24.04 compatibility, and publishing package with provenance.
  • Other changes: Refactor code and tests for dependency compatibility, update support table and fix some links in the README.

See the migration guide for details.

Full changelog

3.1.0...4.0.0

Changelog

Sourced from pa11y-ci's changelog.

4.1.1 (2026-05-11)

Pa11y CI 4.1.1 updates the lodash dependency to ~4.18.1 to resolve GHSA-f23m-r3pf-42r / CVE-2026-2950.

4.1.0 (2026-03-02)

  • Add support for config files with the .cjs extension
  • Improve documentation for sitemap-exclude
  • Improve npm keywords for better discoverability
  • Replace nyc with c8 for test coverage
  • Replace mockery with quibble for mocking
  • Upgrade dependencies to recent versions matching pa11y's to ensure deduplication works well

New Contributors

Full Changelog: pa11y/pa11y-ci@4.0.1...4.1.0

4.0.1 (2025-08-15)

Pa11y CI 4.0.1 reintroduces compatibility for node >=20.0.0 <20.18.1. (At the time of writing, v20.19.4 is the latest version of node 20.)

Pa11y CI 4.0.0 updated the cheerio dependency to 1.1.2. But this causes EBADENGINE warnings when installing, if node <20.18.1. We target compatibility with node >=20, which after some discussion we think should mean >=20.0.0.

Full changelog

4.0.0...4.0.1

4.0.0 (2025-07-22)

Pa11y CI 4.0.0 requires a stable (even-numbered) Node.js version of 20 or above, updates to the latest version of Pa11y (9) and Puppeteer (24), updates several other dependencies, and includes some GitHub actions and documentation cleanup. See the migration guide for details.

Changes

  • Breaking: Upgrade Node.js support: Pa11y CI 4 requires a stable (even-numbered) Node.js version of 20 or above, dropping support for Node 12, 14, 16, 18.
  • Breaking: Upgrade pa11y to 9 (from 6), which updates numerous dependencies, fixes issues with Pa11y CI failing to run on Ubuntu 24.04, and resolves several vulnerabilities and deprecated packages (closing #198, #227, #242, #247).
    • Upgrade puppeteer to 24 (from 9.1), which updates to the current Chrome. This changes Chrome's default headless mode, see the migration guide for details. Also expand the puppeteer dependency compatibility to caret (patch and minor releases) to allow upgrades to a more recent compatible version upon install (which frequently contains Chrome updates and security patches).
    • Upgrade axe-core to 4.10 from 4.2. This includes rule fixes that may change results when using the axe runner. See axe-core releases for complete details.
    • Upgrade semver to 7.7 from 7.3, resolving CVE-2022-25883.
  • Fixed issue with pa11y-ci process hanging if browser passed from config file. (#248)
  • Other dependency upgrades: commander to 14.0, async to 3.2, cheerio to 1.1, and node-fetch to 2.7.
  • GitHub Actions changes: Update workflows for supported Node version, Ubuntu 24.04 compatibility, and publishing package with provenance.
  • Other changes: Refactor code and tests for dependency compatibility, update support table and fix some links in the README.

See the migration guide for details.

Full changelog

3.1.0...4.0.0

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for pa11y-ci since your current version.


Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Bumps [pa11y-ci](https://github.com/pa11y/pa11y-ci) from 3.1.0 to 4.1.1.
- [Release notes](https://github.com/pa11y/pa11y-ci/releases)
- [Changelog](https://github.com/pa11y/pa11y-ci/blob/main/CHANGELOG.md)
- [Commits](pa11y/pa11y-ci@3.1.0...4.1.1)

---
updated-dependencies:
- dependency-name: pa11y-ci
  dependency-version: 4.1.1
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Aug 17, 2026

Copy link
Copy Markdown
Author

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants