v11.1.0

Minor Changes

• e83f61c #99 Thanks @jonrohan! - Create a no-deprecated-colors rule that looks for deprecated css color variables from primer/primitives.

Patch Changes

• 581f40a #105 Thanks @jonrohan! - Adding reporting to the linter to know how many variables are replaced

v10.0.1

Patch Changes

• aa76171 #90 Thanks @jonrohan! - Updating the no-undefined-variables lint for the new color-variables mixin.

v11.0.0

• Remove rules that clash with prettier (#89)

v10.0.0...v11.0.0

v9.3.3

Patch Changes

• a339c69 #81 Thanks @BinaryMuse! - Update globby to v11

v9.3.2

Patch Changes

• d18cfbf #79 Thanks @BinaryMuse! - Add additinal verbose logging to no-undefined-vars

• d18cfbf #79 Thanks @BinaryMuse! - Fix handling of edge-cases in no-undefined-vars

• bb07673 #76 Thanks @BinaryMuse! - Set the default verbose option for no-scale-colors to false

v9.3.0

🐛 Bug Fixes

• The no-undefined-vars rule now understands variables defined with @include color-mode-var(...)
• The no-undefined-vars rule now checks the last two parameters of the @include color-mode-var(...) mixin to ensure any CSS variables referenced are defined

🚀 Enhancements

• Added no-scale-colors rule to ensure bare scale colors (which begin with --color-scale- or --color-auto-) are not used as property values

v9.2.4

🐛 Bug fixes

• Fix variable recognition when fallback values are present

v9.2.3

🐛 Bug fixes

• Fix no-undefined-vars to support values with CSS variable fallbacks

v9.2.2

🐛 Bug fixes

• Update string.prototype.matchall to fix a transitive dependency issue

v9.2.1

🐛 Bug fixes

• Fix slow runtime by caching variable definitions in primer/no-undefined-vars rule
• Fix duplicate errors in primer/no-undefined-vars rule