bjankord / stylelint-config-sass-guidelines

βš™ A stylelint config inspired by https://sass-guidelin.es/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

An in-range update of stylelint-scss is breaking the build 🚨

greenkeeper opened this issue Β· comments

The dependency stylelint-scss was updated from 3.13.0 to 3.14.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

stylelint-scss is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ Node 12 on ubuntu-latest: null
  • ❌ Node 10 on ubuntu-latest: null
  • ❌ Node 8.16.2 on ubuntu-latest: null

Release Notes for 3.14.0
  • Added: support for stylelint version 13.
  • Fixed: avoid possible breaking changes in the future by not using stylelint's internal utility functions.
Commits

The new version differs by 21 commits.

  • e005ff5 Prepare version 3.14.0 [skip ci]
  • 801cc98 Update contributors list [skip ci]
  • fd2922e Merge pull request #437 from kristerkari/lodash
  • 2d48896 Switch back to using the lodash package.
  • 4ea73e7 Merge pull request #428 from kristerkari/stylelint-13
  • 1445870 Add new upstream files for Stylelint v13.0.0 compatibility.
  • aa2e809 Update stylelint to v13.0.0
  • d23e3d7 Merge pull request #435 from kristerkari/stylelint-api
  • c2a0a60 Merge pull request #446 from kristerkari/deps-2
  • 01e8806 Update devDependencies
  • 34afdcc Update devDepencies. (#444)
  • f2c7cf0 Remove eslint-plugin-sort-requires (#436)
  • fb6c418 Fix typo in comment
  • 0905db6 Stop using private Stylelint code
  • ba1fa12 Merge pull request #427 from kristerkari/deps

There are 21 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

After pinning to 3.13.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.