v7.0.1 (June 20, 2019)

🐛 This patch release fixes #32 by loosening the peer dependency version specifier for @primer/css so that the config works with any version of Primer CSS after primer/css#666.

📦 We've also upgraded to jest@24.8.0 to resolve some dependency vulnerabilities.

v7.0.0

💥 Breaking changes

• The config now uses primer/no-override instead of primer/selector-no-utility. See #25 for more info.
• @primer/css is now a required peer dependency, because we want this to work with different versions of Primer.

🚀 Features

• primer/no-override is a new rule that replaces primer/selector-no-utility and makes it possible to configure files or directories with options that allow or prevent overrides of selectors from different Primer CSS "bundles". See #25 for more info.

🏠 Internal

• There are more extensive tests, additional expect() matchers, and test utilities that make it easy to set rule options in each test.

v6.0.0 (2019-03-18)

TL;DR: this release requires @primer/css as a peer dependency. If you really don't want that, you -should be able to disable primer/selector-no-utility in your config and prevent it from being loaded.

💥 Breaking changes

• This release includes stylelint-selector-no-utility@4.0.0, which is a breaking change because it (and now, this module) requires @primer/css as a peer dependency so that we can pull the list of immutable utility classes from the module at runtime rather than building them at publish time.

4.0.1 - publish action

This is a maintenance release that adds the primer/publish action to automatically publish to npm when we merge to master. 🌈 🦄 🚀

v4.0.0

This is a major release that bumps two of our major dependencies (stylelint-scss and stylelint-order) by two major versions each, and reintroduces this package as a separate repository on GitHub. (See primer/css#652 for more info.)

v2.0.0

💥 Breaking changes

The following updates are breaking changes, since comments that disable the deprecated rules will now produce (failing) linting errors. Please update your stylelint-disable statements accordingly:

• Replaced selector-no-id: true with selector-max-id: 0
• Replaced selector-no-type: true with selector-max-type: 0

Updates

The rest of the changes should not introduce new linting errors:

• Updated: moved browserslist spec to package.json
• Updated: using the no-unsupported-browser-features plugin instead of the deprecated no-unsupported-browser-features rule
• Removed: media-feature-no-missing-punctuation
• Updated: replaced rule-nested-empty-line-before and rule-non-nested-empty-line-before with rule-empty-line-before