The devDependency eslint-plugin-react was updated from 7.12.2 to 7.12.3.

🚨 View failing branch.

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

eslint-plugin-react 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

• ❌ Travis CI - Branch: The build failed.

---

Release Notes for v7.12.3

Fixed

• jsx-indent: Prevent crash on valueless props (#2120, @jomasti)
• jsx-fragments: avoid crashing on self-closing fragments (#2113, @alexzherdev)
• no-unused-prop-types: Fix propType detection inside class bodies (#2115, @drx)
• no-unused-prop-types: fix issue with propTypes misclassifying props (#2111, @drx)
• display-name: fix false positive for React.memo (#2109, @jomasti)

Changed

• [Docs] add a missing comma in the JSON settings (#2117, @haideralsh)
• [Docs] update README to document React version detection (#2114, @mohsinulhaq)

Commits

The new version differs by 14 commits.

• 2f5cec9 Update CHANGELOG and bump version
• 096161a Merge pull request #2120 from jomasti/issue-2119
• 9d3955a Prevent crash of jsx-indent rule
• 230c7e0 Merge pull request #2117 from haideralsh/patch-1
• b4b0e72 fix: add a missing in the JSON settings
• d2aa260 Merge pull request #2115 from drx/class_body_prop_types
• 41974e5 Fix propType detection inside class bodies
• 40f2565 [Docs] update README to document React version detection
• dd0757f Merge pull request #2113 from alexzherdev/2112-fix-self-closing-fragments
• e997f6c [Fix] avoid crashing on self-closing fragments
• b48b479 Merge pull request #2111 from drx/prop_types_class_properties
• e15bafa [Fix] no-unused-prop-types: fix issue with propTypes misclassifying props
• a86b339 Merge pull request #2109 from jomasti/issue-2105
• 5f9863e Fix display-name false positive for React.memo

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 🌴

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Is your feature request related to a problem? Please describe.
I like being able to set an exact timeout, but sometimes i just want the update to run at specific update times, like the 10 minutes around the top of the hour for a minute each, then not to run most of the rest of the time.

Describe the solution you'd like
It would be great to be able to use something like node-cron syntax to set my update schedule, and for that to supersede timeout updates.

Describe alternatives you've considered
I've considered using something that evaluates the time to the next interval if you provide a keyword like hourly instead of the current "timeout" numeric requirement, but I don't think it makes sense to add all of that logic to the library.

Additional context
None I can think of

The devDependency @types/chai was updated from 4.2.0 to 4.2.1.

🚨 View failing branch.

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

@types/chai 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

• ❌ Travis CI - Branch: The build failed.

---

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 🌴

The devDependency semantic-release was updated from 15.10.4 to 15.10.5.

🚨 View failing branch.

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

semantic-release 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

• ❌ Travis CI - Branch: The build failed.

---

Release Notes for v15.10.5

15.10.5 (2018-10-20)

Bug Fixes

• include release notes in JS API result for dry mode (3411520)

Commits

The new version differs by 1 commits.

• 3411520 fix: include release notes in JS API result for dry mode

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 🌴

The devDependency eslint-plugin-jsx-a11y was updated from 6.2.1 to 6.2.2.

🚨 View failing branch.

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

eslint-plugin-jsx-a11y 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

• ❌ Travis CI - Branch: The build failed.

---

Commits

The new version differs by 102 commits.

• 057fb27 6.2.2
• fc56208 Merge pull request #615 from evcohen/changelog--v6.2.2
• 8c5f964 Changelog for v6.2.2
• f82fbcb Merge pull request #614 from evcohen/update--jsx-ast-utils
• 1c3e63a Update jsx-ast-utils to v2.2.1
• c571293 Merge pull request #613 from evcohen/add-babel-to-dev-deps
• c398d3a Add @babel/cli to the dev dependencies
• 13b370c Merge pull request #610 from evcohen/greenkeeper/flow-bin-0.102.0
• e28b81a Merge branch 'master' into greenkeeper/flow-bin-0.102.0
• e3163e3 Merge pull request #603 from evcohen/another-attempt-at-eslint-v6
• f121a78 Merge branch 'master' into another-attempt-at-eslint-v6
• f3de162 Merge pull request #611 from evcohen/update-jsx-ast-utils
• 91f17be Update ESLint to v6
• 1eb9f19 Update jsx-ast-utils to 2.2.0
• 313bc03 chore(package): update flow-bin to version 0.102.0

There are 102 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 🌴

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀