search

postcss / postcss-cli

CLI for postcss
Other
840 stars 93 forks source link

Update postcss-load-config to the latest version 🚀 #226

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 6 years ago

Version 2.0.0 of postcss-load-config was just published.

Dependency postcss-load-config
Current Version 1.2.0
Type dependency

The version 2.0.0 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of postcss-load-config.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

Release Notes v2.0.0

2018-07-10

Bug Fixes

  • package: require-from-string memory leak, updates cosmiconfig v2.1.0...4.0.0 (dependencies) (17f9621)
  • src/index.js: clone the config {Object} on assignment instead of mutating it (8669a90)

Features

  • src: load plugins from the current working directory (9745bf0)
  • src: show config file in err.message (4baff47)

BREAKING CHANGES

  • package: requires node >= v4.0.0
  • package: removes argv option (options.argv)
  • package: removes --config parsing
Commits

The new version differs by 38 commits.

  • dbf5469 chore(release): 2.0.0
  • 7681868 build(commitlint): remove commit linting
  • 39ad81e docs(README): rewording and formatting updates
  • 0bb7c8f chore(.github/ISSUE_TEMPLATE): add about front matter
  • adae169 test(*): simplify structure
  • 8669a90 fix(src/index.js): clone the config {Object} on assignment instead of mutating it
  • 17f9621 fix(package): require-from-string memory leak, updates cosmiconfig v2.1.0...4.0.0 (dependencies)
  • 9745bf0 feat(src): load plugins from the current working directory
  • 14f3e53 chore(package): update devDependencies
  • 4baff47 feat(src): show config file in err.message
  • 983d7ba docs(INDEX.md): rename to DOCS.md
  • 029540d docs(CONTRIBUTING.md): update guide
  • 4fc6ff0 ci(appveyor.yml): add node lts/* && stable
  • 7e8c7e9 ci(.travis.yml): add node lts/* && stable
  • dad0d96 chore(.npmignore): update ignore list

There are 38 commits in total.

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper bot :palm_tree:

coveralls commented 6 years ago

Coverage Status

Coverage remained the same at 74.648% when pulling 1788d195ef3728758f191508eb2e87aec42b5775 on greenkeeper/postcss-load-config-2.0.0 into 3b6b176f7ce828a6b2f1f5564f632577e13f13aa on master.

RyanZim commented 6 years ago

Will need to quit passing argv: false option, since the default behavior is now what we want.