chore(deps-dev): bump @sa11y/jest from 3.0.0 to 3.1.0

[dependabot[bot]]

Bumps @sa11y/jest from 3.0.0 to 3.1.0.

Release notes

Sourced from @​sa11y/jest's releases.

fix: automatic checks file filter to be exclusion only

Fix 🐛

• automatic checks file filter to be exclusion only to keep it simple
  • the filter was trying to do both inclusion and exclusion which led to complicated buggy code
• add sa11y common pkg as dep instead of dev dep (fixes #83)

PRs

• #84

fix: empty results error caused by filtering out non-a11y errors

Reverts 🐛

• filtering of non-a11y results introduced in #78 for automatic checks
  • as it is causing issues with certain CI workflows that produce no test results file

PRs

• fix: empty results error caused by filtering out non-a11y errors

refactor: exclude descendancy based rules from Jest API and non-a11y failures from custom reporter

Refactor ♻️

• exclude descendancy rules from Jest API
  • these are rules that might fail at unit/component level but might pass at page level
• change sa11y results processor to output only a11y failures

PRs

• [refactor: exclude descendancy based rules from Jest API and non-a11y failures from custom reporter by mohanraj-r · Pull Request #78 · salesforce/sa11y](salesforce/sa11y#78)

Changelog

Sourced from @​sa11y/jest's changelog.

3.1.0 (2021-11-18)

Bug Fixes

• automatic checks file filter to be exclusion only to keep it simple
• add sa11y common pkg as dep instead of dev dep

3.0.2 (2021-11-02)

Reverts

• filtering of non-a11y results introduced in 3.0.1
  • as it is causing issues with certain CI workflows that produce no test results file

3.0.1 (2021-10-21)

Refactor

• exclude descendancy rules from Jest API
  • these are rules that might fail at unit/component level but might pass at page level
• change sa11y results processor to output only a11y failures

Commits

• 6c900d7 fix: automatic checks file filter to be exclusion only to keep it simple (#84)
• 32b02b7 fix: empty results error caused by filtering out non-a11y errors (#81)
• 93de21f refactor: exclude descendancy based rules from Jest API and non-a11y failure...
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@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)

[github-actions[bot]]

Ok, no one seems to work on this. Closing it now. 👋

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.