v4.1.1

4.1.1 (2022-12-28)

v4.1.0

4.1.0 (2022-12-15)

Features

• add OSSF Scorecard action and badge (#292) (c2d36dc)

v4.0.1

4.0.1 (2022-11-17)

Bug Fixes

• build before packaging (#262) (47883aa)

v4.0.0

4.0.0 (2022-10-20)

⚠ BREAKING CHANGES

• Explicitly supporting NodeJS 14.x and 16.x
• sa11y will no longer support Node.js 12, which is EOL since 30 April 2022

Features

• remove support for Node.js 12 (#116) (43ade48)
• semantic release (#227) (6b7a180)
• tsconfig package for tsconfig.json (#174) (5ff2fd2)
• webdriver7 (#150) (70dafc2)

Bug Fixes

• set package.json node engines (#228) (42de911)

v4.0.0-alpha.7

4.0.0-alpha.7 (2022-10-19)

Bug Fixes

• ci: node auth token had extra character (c387311)
• troubleshoot npm auth (72da605)

v4.0.0-alpha.1

4.0.0-alpha.1 (2022-10-14)

⚠ BREAKING CHANGES

• sa11y will no longer support Node.js 12, which is EOL since 30 April 2022

Features

• remove support for Node.js 12 (#116) (43ade48)
• semantic-release (18d2728)
• tsconfig package for tsconfig.json (#174) (5ff2fd2)
• webdriver7 (#150) (70dafc2)

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

chore: move to unified versioning of @sa11y packages instead of independent versioning

Chore 🧹

• Moving to unified versioning of @sa11y packages instead of independent versioning for reducing complexity of managing independent versions
• No code changes, No breaking changes
• This is a one-off switch and semantic versioning will be used going forward

Version bump

• @sa11y/assert: 1.0.0 => 3.0.0
• @sa11y/browser-lib: 1.0.1 => 3.0.0
• @sa11y/common: 0.4.0 => 3.0.0
• @sa11y/format: 0.5.0 => 3.0.0
• @sa11y/jest: 1.1.0 => 3.0.0
• @sa11y/preset-rules: 1.0.1 => 3.0.0
• @sa11y/wdio: 2.0.2-beta.0 => 3.0.0
• @sa11y/test-integration: 0.2.4 => 3.0.0 (private)
• @sa11y/test-utils: 0.4.3 => 3.0.0 (private)

PR

• chore: move to unified versioning for all @sa11y pkgs