Code Monkey home page Code Monkey logo

css-filter's People

Contributors

comandeer avatar greenkeeper[bot] avatar greenkeeperio-bot avatar

Stargazers

 avatar

Watchers

 avatar  avatar

css-filter's Issues

An in-range update of uglify-js is breaking the build 🚨

Version 2.8.14 of uglify-js just got published.

Branch Build failing 🚨
Dependency uglify-js
Current Version 2.8.13
Type devDependency

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

As uglify-js is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
Release Notes v2.8.14

Β 

Commits

The new version differs by 8 commits .

  • 30a7504 v2.8.14
  • a3cc3a9 make expect_stdout work on Node.js 0.12 (#1623)
  • 96f8bef fix commit 88fb83a (#1622)
  • cd58635 fix AST_Binary.lift_sequences() (#1621)
  • 274331d transform String.charAt() to index access (#1620)
  • 0489d6d handle runtime errors in expect_stdout (#1618)
  • fb09283 fix top-level directives in compress tests (#1615)
  • b7c112e Add --in-source-map inline documentation (#1611)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of husky is breaking the build 🚨

Version 0.13.4 of husky just got published.

Branch Build failing 🚨
Dependency husky
Current Version 0.13.3
Type devDependency

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

As husky is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
  • ❌ codecov/project 66.19% (-33.81%) compared to 8e4936e Details
  • βœ… codecov/patch Coverage not affected when comparing 8e4936e...ac834fa Details

Commits

The new version differs by 9 commits.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup-plugin-uglify is breaking the build 🚨

Version 1.0.2 of rollup-plugin-uglify just got published.

Branch Build failing 🚨
Dependency rollup-plugin-uglify
Current Version 1.0.1
Type devDependency

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

As rollup-plugin-uglify is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
Commits

The new version differs by 12 commits .

  • e01c74e 1.0.2
  • 421ac78 Merge pull request #27 from anmonteiro/patch-1
  • 9b5d413 fix harmony code example
  • 157bc49 Merge pull request #26 from jhabdas/master
  • 89c03e4 Update instructions for use of Harmony
  • 6cff2dd Merge pull request #19 from ratson/js-ext
  • 6a556d6 Add module field
  • dd175e5 Preserve .js filename extension
  • 7d82545 Merge pull request #17 from Grawl/patch-2
  • e4416ed Update README.md
  • 9a7fef3 Merge pull request #16 from Grawl/patch-1
  • cc49f94 Add options to documentation

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of karma-sinon-chai is breaking the build 🚨

Version 1.3.0 of karma-sinon-chai just got published.

Branch Build failing 🚨
Dependency karma-sinon-chai
Current Version 1.2.4
Type devDependency

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

As karma-sinon-chai is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
Commits

The new version differs by 2 commits .

  • 1d15460 1.3.0
  • bca7e7a chore(deps): bump dependencies to latest versions (#44)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup-plugin-node-resolve is breaking the build 🚨

Version 2.1.1 of rollup-plugin-node-resolve just got published.

Branch Build failing 🚨
Dependency rollup-plugin-node-resolve
Current Version 2.1.0
Type devDependency

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

As rollup-plugin-node-resolve is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details

  • βœ… codecov/patch Coverage not affected when comparing 8e4936e...78f0055 Details

  • ❌ codecov/project 66.19% (-33.81%) compared to 8e4936e Details

Commits

The new version differs by 7 commits .

  • c944373 -> v2.1.1
  • a427757 Merge pull request #95 from rollup/gh-93
  • cb168f9 ignore jail if not supplied (#93)
  • e1fb0eb update appveyor config
  • c375c93 Merge pull request #92 from GGAlanSmithee/patch-1
  • ea088a6 Minor README.md correction
  • 66e42bc update README

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of jsdoc is breaking the build 🚨

Version 3.5.0 of jsdoc just got published.

Branch Build failing 🚨
Dependency jsdoc
Current Version 3.4.3
Type devDependency

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

As jsdoc is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes JSDoc 3.5.0

This version of JSDoc includes the following major changes:

  • JSDoc now uses the Babylon JavaScript parser, which means that
    JSDoc can parse any JavaScript or JSX file that is supported by the Babel
    compiler.
  • You can now use a JavaScript file to configure JSDoc. See the
    documentation for details and examples.
  • Fixed multiple issues with documenting ES2015 classes and modules.
  • JSDoc now requires Node.js 4.2.0 or later.

For a complete list of changes, see the changelog on GitHub.

Commits

The new version differs by 112 commits ahead by 112, behind by 45.

  • cdd00c0 3.5.0
  • 50d6119 update 3.5.0 changelog
  • e94a598 3.5.0 changelog
  • 5d0b690 reformat changelog
  • c50a4c0 add yields tag (#1388)
  • f31a011 resolve the path to the JS config file before requiring it (#1386)
  • d95cbdd support namespaces that are also functions (#955)
  • 9f8853a add hideconstructor tag (#952)
  • ca1c4f2 add package tag (#962)
  • 6275e69 autodetect default and repeatable parameters when a function is assigned to a variable (#1054)
  • 0e4f1a9 correctly document constructors and instance properties of ES2015 classes (#1182)
  • 67db938 add sourceType config option
  • f101798 fix crash when the author tag is empty (#1289)
  • 43a117d add recurseDepth config option (#1340)
  • 8f5c60b support bigint

There are 112 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of sinon-chai is breaking the build 🚨

Version 2.10.0 of sinon-chai just got published.

Branch Build failing 🚨
Dependency sinon-chai
Current Version 2.9.0
Type devDependency

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

As sinon-chai is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/Comandeer/css-filter/builds/227497448?utm_source=github_status&utm_medium=notification)

Release Notes 2.10.0

Added the calledImmediatelyBefore() and calledImmediatelyAfter() asserters.

Commits

The new version differs by 3 commits0.

  • 9aa5a73 Version 2.10.0
  • 4d32c50 Add a test showing that #94 is not a problem
  • f0628a1 Add calledImmediatelyBefore/calledImmediatelyAfter

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.41.2 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.41.1
Type devDependency

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

As rollup is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Commits

The new version differs by 9 commits .

  • e2d9b6b -> v0.41.2
  • 2a01a99 Merge pull request #1241 from kzc/0_41_0_changelog_addition
  • c038cda Merge pull request #1240 from rollup/gh-841-updated
  • 61528b7 change log addition for 0.41.0
  • 82b284d optimize ns["foo"] (#841)
  • 40a0ed5 Merge pull request #1239 from rollup/gh-1213
  • bc0f791 suppress warnings with --silent (closes #1213)
  • 6384b6c Merge pull request #1238 from rollup/gh-797
  • 101ad28 use options.indent for UMD block - fixes #797

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of rollup-plugin-commonjs is breaking the build 🚨

Version 8.1.0 of rollup-plugin-commonjs just got published.

Branch Build failing 🚨
Dependency rollup-plugin-commonjs
Current Version 8.0.2
Type devDependency

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

As rollup-plugin-commonjs is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 12 commits.

  • f7602d9 -> v8.1.0
  • 60846f5 Merge pull request #212 from rollup/external-from-commonjs
  • 5309d9b update appveyor config
  • d4a14e3 lint
  • d81bca9 handle options.external correctly
  • a5718e2 Merge branch 'master' into external-from-commonjs
  • cb0f14e just test in node 8
  • 078332b failing test for external module imported from commonjs
  • 61157df Merge pull request #195 from calvinmetcalf/top-level-return
  • bcadeb1 Drop extra linebreak from tests (#205)
  • c831ca4 Include a regexp in options' documentation (#197)
  • bb3045d top level return support

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of commitplease is breaking the build 🚨

Version 2.7.10 of commitplease just got published.

Branch Build failing 🚨
Dependency commitplease
Current Version 2.7.9
Type devDependency

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

As commitplease is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/Comandeer/css-filter/builds/227125569?utm_source=github_status&utm_medium=notification)

Commits

The new version differs by 2 commits0.

  • 1448cde 2.7.10
  • 0b2dbbf Move guidelinesUrl from index.js into defaults.js

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of karma-chrome-launcher is breaking the build 🚨

Version 2.1.0 of karma-chrome-launcher just got published.

Branch Build failing 🚨
Dependency karma-chrome-launcher
Current Version 2.0.0
Type devDependency

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

As karma-chrome-launcher is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/Comandeer/css-filter/builds/228038045?utm_source=github_status&utm_medium=notification)

Release Notes v2.1.0

Features

  • add support for custom user-data-dir in Chromium (579fcfc), closes #89
  • add support for headless Chrome/ChromeCanary (7446181)
Commits

The new version differs by 19 commits0.

  • 2267df1 chore: release v2.1.0
  • f993c48 chore: update contributors
  • 7446181 feat: add support for headless Chrome/ChromeCanary
  • d81da0e Merge pull request #116 from maieutiquer/patch-1
  • 37513a9 clean-up irrelevant comment
  • a0235a2 Merge pull request #115 from karma-runner/greenkeeper-standard-10.0.0
  • 8987630 chore(package): update standard to version 10.0.0
  • 1e4b4ff Merge pull request #110 from karma-runner/greenkeeper-standard-9.0.2
  • 5d559e7 chore(package): update standard to version 9.0.2
  • fbe91ca Merge pull request #92 from karma-runner/greenkeeper-grunt-auto-release-0.0.7
  • 4a7efc0 chore(package): update grunt-auto-release to version 0.0.7
  • 7abf72d Merge pull request #109 from karma-runner/greenkeeper-sinon-2.0.0
  • e4d38c0 chore(package): update sinon to version 2.0.0
  • b9f9214 Merge pull request #84 from karma-runner/greenkeeper-mocha-3.2.0
  • f5c5874 Merge branch 'master' into greenkeeper-mocha-3.2.0

There are 19 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of cz-conventional-changelog is breaking the build 🚨

Version 2.1.0 of cz-conventional-changelog was just published.

Branch Build failing 🚨
Dependency cz-conventional-changelog
Current Version 2.0.0
Type devDependency

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

cz-conventional-changelog is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
  • ❌ codecov/project 66.19% (-33.81%) compared to 8e4936e Details
  • βœ… codecov/patch Coverage not affected when comparing 8e4936e...a29a54e Details

Release Notes v2.1.0

<a name"2.1.0">

2.1.0 (2017-10-27)

Features

  • prompt: add confirmation fields + edit for clarity (#58) (d40ac2c5)
Commits

The new version differs by 3 commits.

  • d40ac2c feat(prompt): add confirmation fields + edit for clarity (#58)
  • f7a770e Merge pull request #57 from Epitrochoid/remove-unused-dep
  • 2d1095b Removed unused pad-right dependency

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 🌴

An in-range update of mocha is breaking the build 🚨

Version 3.3.0 of mocha just got published.

Branch Build failing 🚨
Dependency mocha
Current Version 3.2.0
Type devDependency

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

As mocha is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/Comandeer/css-filter/builds/225158401),- ❌ **codecov/project** 66.19% (-33.81%) compared to 8e4936e [Details](https://codecov.io/gh/Comandeer/css-filter/commit/1f37665937a38c11422fda07726dc0f75db5b6d6),- βœ… **codecov/patch** Coverage not affected when comparing 8e4936e...1f37665 [Details](https://codecov.io/gh/Comandeer/css-filter/commit/1f37665937a38c11422fda07726dc0f75db5b6d6)

Release Notes coverave

Thanks to all our contributors, maintainers, sponsors, and users! ❀️

As highlights:

  • We've got coverage now!
  • Testing is looking less flaky \o/.
  • No more nitpicking about "mocha.js" build on PRs.

πŸŽ‰ Enhancements

  • #2659: Adds support for loading reporter from an absolute or relative path (@sul4bh)
  • #2769: Support --inspect-brk on command-line (@igwejk)

πŸ› Fixes

  • #2662: Replace unicode chars w/ hex codes in HTML reporter (@rotemdan)

πŸ” Coverage

πŸ”© Other

Commits

The new version differs by 89 commits0.

  • fb1687e :ship: Release v3.3.0
  • 1943e02 Add Changelog for v3.3.0
  • 861e968 Refactor literal play-icon hex code to a var
  • 1d3c5bc Fix typo in karma.conf.js
  • 9bd9389 Fix spec paths in test HTML files
  • 0a93024 Adds tests for loading reporters w/ relative/absolute paths (#2773)
  • 73929ad Comment special treatment of '+' in URL query parsing
  • e2c9514 Merge pull request #2769 from igwejk/support_inspect_break_in_opts
  • 038c636 Support --inspect-brk on command-line
  • b4ebabd Merge pull request #2727 from lamby/reproducible-build
  • 882347b Please make the build reproducible.
  • a2fc76c Merge pull request #2703 from seppevs/cover_utils_some_fn_with_tests
  • ed61cd0 cover .some() function in utils.js with tests
  • f42cbf4 Merge pull request #2701 from craigtaub/landingSpec
  • 6065242 use stubbed symbol

There are 89 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of eslint is breaking the build 🚨

Version 3.19.0 of eslint just got published.

Branch Build failing 🚨
Dependency eslint
Current Version 3.18.0
Type devDependency

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

As eslint is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details

  • ❌ codecov/project 66.19% (-33.81%) compared to 8e4936e Details

  • βœ… codecov/patch Coverage not affected when comparing 8e4936e...a4d5d88 Details

Release Notes v3.19.0
  • e09132f Fix: no-extra-parens false positive with exports and object literals (#8359) (Teddy Katz)
  • 91baed4 Update: allow custom messages in no-restricted-syntax (fixes #8298) (#8357) (Vitor Balocco)
  • 35c93e6 Fix: prevent space-before-function-paren from checking type annotations (#8349) (Teddy Katz)
  • 3342e9f Fix: don't modify operator precedence in operator-assignment autofixer (#8358) (Teddy Katz)
  • f88375f Docs: clarify that no-unsafe-negation is in eslint:recommended (#8371) (Teddy Katz)
  • 02f0d27 Docs: Add soda0289 to Development Team (#8367) (Kai Cataldo)
  • 155424c Fix: ignore empty path in patterns (fixes #8362) (#8364) (alberto)
  • 27616a8 Fix: prefer-const false positive with object spread (fixes #8187) (#8297) (Vitor Balocco)
  • 8569a90 Docs: add note about git's linebreak handling to linebreak-style docs (#8361) (Teddy Katz)
  • 5878593 Chore: fix invalid syntax in no-param-reassign test (#8360) (Teddy Katz)
  • 1b1046b Fix: don't classify plugins that throw errors as "missing" (fixes #6874) (#8323) (Teddy Katz)
  • 29f4ba5 Fix: no-useless-computed-key invalid autofix for getters and setters (#8335) (Teddy Katz)
  • 0541eaf Fix: no-implicit-coercion invalid autofix with consecutive identifiers (#8340) (Teddy Katz)
  • 41b9786 Fix: no-extra-parens false positive with objects following arrows (#8339) (Teddy Katz)
  • 3146167 Fix: eslint.verify should not mutate config argument (fixes #8329) (#8334) (alberto)
  • 927de90 Fix: dot-notation autofix produces invalid syntax for integer properties (#8332) (Teddy Katz)
  • a9d1bea Fix: comma-style autofix produces errors on parenthesized elements (#8331) (Teddy Katz)
  • d52173f Fix: don't generate invalid options in config-rule (#8326) (Teddy Katz)
  • 6eda3b5 Fix: no-extra-parens invalid autofix in for-of statements (#8337) (Teddy Katz)
  • 6c819d8 Fix: dot-notation autofix produces errors on parenthesized computed keys (#8330) (Teddy Katz)
  • 2d883d7 Fix: object-shorthand autofix produces errors on parenthesized functions (#8328) (Teddy Katz)
  • cd9b774 Fix: quotes false positive with backtick option in method names (#8327) (Teddy Katz)
  • d064ba2 Fix: no-else-return false positive for ifs in single-statement position (#8338) (Teddy Katz)
  • 6a718ba Chore: enable max-statements-per-line on ESLint codebase (#8321) (Teddy Katz)
  • 614b62e Chore: update sinon calls to deprecated API. (#8310) (alberto)
  • 0491572 Chore: use precalculated counts in codeframe formatter (#8296) (Vitor Balocco)
  • 8733e6a Chore: Fix incorrect error location properties in tests (#8307) (alberto)
  • c4ffb49 Chore: Fix typos in test option assertions (#8305) (Teddy Katz)
  • 79a97cb Upgrade: devDependencies (#8303) (alberto)
  • e4da200 Upgrade: Mocha to 3.2.0 (#8299) (Ilya Volodin)
  • 2f144ca Fix: operator-assignment autofix errors with parentheses (fixes #8293) (#8294) (Teddy Katz)
  • 7521cd5 Chore: update token logic in rules to use ast-utils (#8288) (Teddy Katz)
  • 9b509ce Chore: refactor space-before-function-paren rule (#8284) (Teddy Katz)
  • ddc6350 Fix: no-param-reassign false positive on destructuring (fixes #8279) (#8281) (Teddy Katz)
  • f8176b3 Chore: improve test coverage for node-event-generator (#8287) (Teddy Katz)
  • 602e9c2 Docs: fix incorrect selector examples (#8278) (Teddy Katz)
Commits

The new version differs by 38 commits .

  • 421aab4 3.19.0
  • 26a4dd5 Build: changelog update for 3.19.0
  • e09132f Fix: no-extra-parens false positive with exports and object literals (#8359)
  • 91baed4 Update: allow custom messages in no-restricted-syntax (fixes #8298) (#8357)
  • 35c93e6 Fix: prevent space-before-function-paren from checking type annotations (#8349)
  • 3342e9f Fix: don't modify operator precedence in operator-assignment autofixer (#8358)
  • f88375f Docs: clarify that no-unsafe-negation is in eslint:recommended (#8371)
  • 02f0d27 Docs: Add soda0289 to Development Team (#8367)
  • 155424c Fix: ignore empty path in patterns (fixes #8362) (#8364)
  • 27616a8 Fix: prefer-const false positive with object spread (fixes #8187) (#8297)
  • 8569a90 Docs: add note about git's linebreak handling to linebreak-style docs (#8361)
  • 5878593 Chore: fix invalid syntax in no-param-reassign test (#8360)
  • 1b1046b Fix: don't classify plugins that throw errors as "missing" (fixes #6874) (#8323)
  • 29f4ba5 Fix: no-useless-computed-key invalid autofix for getters and setters (#8335)
  • 0541eaf Fix: no-implicit-coercion invalid autofix with consecutive identifiers (#8340)

There are 38 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of karma-html2js-preprocessor is breaking the build 🚨

Version 1.1.0 of karma-html2js-preprocessor just got published.

Branch Build failing 🚨
Dependency karma-html2js-preprocessor
Current Version 1.0.0
Type devDependency

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

As karma-html2js-preprocessor is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 6 commits.

  • fef0474 chore(travis): install latest npm
  • c89b01c chore: release v1.1.0
  • 0f43599 chore: update contributors
  • c6a3f25 chore: update dependencies
  • 7f54b6a Merge pull request #13 from lazd/issue/12
  • 63f5e77 feat: Added stripPrefix, prependPrefix, and processPath options, closes #12

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of karma is breaking the build 🚨

Version 1.7.0 of karma just got published.

Branch Build failing 🚨
Dependency karma
Current Version 1.6.0
Type devDependency

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

As karma is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes v1.7.0

Bug Fixes

  • middleware: change to use vanilla for loop (ac62cc0), closes #2671
  • reporters: Revert the backwards-incompatible log priority order changes (316b944), closes #2582

Features

  • runner: Buffer stdout and stderr for output when errors occur (460d423)
Commits

The new version differs by 11 commits0.

  • 2a847c2 chore: release v1.7.0
  • 47e52e4 chore: update contributors
  • a99dc52 chore: fix lint task
  • 51b4f64 Merge pull request #2682 from wesleycho/fix/for-in
  • ac62cc0 fix(middleware): change to use vanilla for loop
  • 14b6dfd Merge pull request #2664 from LoveIsGrief/feature-karma-2663
  • 722bbbb docs: add notice about casing in exports
  • e93d1e3 Merge pull request #2676 from mgol/log-order-fixes
  • 316b944 fix(reporters): Revert the backwards-incompatible log priority order changes
  • ef62da9 test(reporters): Fix the log suppressing tests
  • 460d423 feat(runner): Buffer stdout and stderr for output when errors occur

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of greenkeeper-postpublish is breaking the build 🚨

Version 1.1.0 of greenkeeper-postpublish just got published.

Branch Build failing 🚨
Dependency greenkeeper-postpublish
Current Version 1.0.1
Type devDependency

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

As greenkeeper-postpublish is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes v1.1.0

<a name"1.1.0">

1.1.0 (2017-07-27)

Features

  • log if webhook call returns invalid data (ebe7084a)
Commits

The new version differs by 6 commits.

  • 7809891 Merge pull request #17 from greenkeeperio/feat/log-webhook-error
  • ebe7084 feat: log if webhook call returns invalid data
  • 08d4476 docs(readme): add Greenkeeper badge
  • addb31f chore(package): update dependencies
  • cf77fdf chore(package): update standard to version 8.0.0 (#5)
  • d947078 chore(package): update dependencies and switch to version ranges

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of babel-preset-es2015 is breaking the build 🚨

Version 6.24.1 of babel-preset-es2015 just got published.

Branch Build failing 🚨
Dependency babel-preset-es2015
Current Version 6.24.0
Type devDependency

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

As babel-preset-es2015 is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

  • ❌ codecov/project 66.19% (-33.81%) compared to 8e4936e Details

  • βœ… codecov/patch Coverage not affected when comparing 8e4936e...bd381e0 Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of lodash.difference is breaking the build 🚨

Version 4.5.0 of lodash.difference just got published.

Branch Build failing 🚨
Dependency lodash.difference
Current Version 4.4.0
Type dependency

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

lodash.difference is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of codecov is breaking the build 🚨

Version 2.2.0 of codecov just got published.

Branch Build failing 🚨
Dependency codecov
Current Version 2.1.0
Type devDependency

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

As codecov is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details,- βœ… codecov/patch Coverage not affected when comparing 8e4936e...4dff215 Details,- ❌ codecov/project 66.19% (-33.81%) compared to 8e4936e Details

Release Notes v2.2.0

Added: Support for Jenkins Blue Ocean
Added: Clear function to remove all discovered reports after uploading
Fix for Gitlab CI

Commits

The new version differs by 8 commits0.

  • 7f8a29b v2.2.0
  • 576b9fe add CI_REPOSITORY_URL to gitlab detection, fix #60
  • 74a44f2 added -C to unlink reports after uploading
  • d1bf5e4 Merge pull request #56 from rochdev/blue-ocean
  • 0a3cea3 Add support for Jenkins Blue Ocean
  • b365cd8 Merge pull request #57 from codecov/fix/cleanup
  • 7f220cc Removing old execSync code from tests
  • 4ba4609 v2.1.0

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.