Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update memoize-one to the latest version 馃殌 #60

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Dec 17, 2018

The dependency memoize-one was updated from 4.1.0 to 5.0.0.

This version is not covered by your current version range.

If you don鈥檛 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.


Find out more about this release.

FAQ and help

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


Your Greenkeeper bot 馃尨

@coveralls
Copy link

Pull Request Test Coverage Report for Build 312

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%

Totals Coverage Status
Change from base Build 287: 0.0%
Covered Lines: 263
Relevant Lines: 263

馃挍 - Coveralls

greenkeeper bot added a commit that referenced this pull request Mar 27, 2019
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 27, 2019

  • The dependency memoize-one was updated from 4.1.0 to 5.0.1.

Update to this version instead 馃殌

Release Notes for 5.0.1

Engineering health

  • Bumping all dev dependencies #56
  • Upgrading to flow 0.95.1 #56
  • Minor internal cleanup of flow types #56

Other

  • Improving language used for argument length checking for the default equality function in the docs #56
Commits

The new version differs by 2 commits.

See the full diff

greenkeeper bot added a commit that referenced this pull request Mar 29, 2019
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 29, 2019

  • The dependency memoize-one was updated from 4.1.0 to 5.0.2.

Update to this version instead 馃殌

Release Notes for 5.0.2
  • Fixing flow issue #58. Caused by using non-standard $ExpectError comment. Thanks @jmansor for the pick up
Commits

The new version differs by 2 commits.

See the full diff

greenkeeper bot added a commit that referenced this pull request Apr 8, 2019
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Apr 8, 2019

  • The dependency memoize-one was updated from 4.1.0 to 5.0.3.

Update to this version instead 馃殌

Commits

The new version differs by 5 commits.

  • da141a7 v5.0.3
  • 795ae46 Bumping deps (#63)
  • 2662e07 Check in equality perf benchmark (#62)
  • dc00d09 Using for loop for improved speed (#59)
  • cbde410 Split function generic into generic types for args and return value (#61)

See the full diff

greenkeeper bot added a commit that referenced this pull request Apr 8, 2019
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Apr 8, 2019

  • The dependency memoize-one was updated from 4.1.0 to 5.0.4.

Update to this version instead 馃殌

greenkeeper bot added a commit that referenced this pull request Jul 9, 2019
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jul 9, 2019

  • The dependency memoize-one was updated from 4.1.0 to 5.0.5.

Update to this version instead 馃殌

greenkeeper bot added a commit that referenced this pull request Aug 21, 2019
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Aug 21, 2019

  • The dependency memoize-one was updated from 4.1.0 to 5.1.0.

Update to this version instead 馃殌

greenkeeper bot added a commit that referenced this pull request Aug 23, 2019
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Aug 23, 2019

  • The dependency memoize-one was updated from 4.1.0 to 5.1.1.

Update to this version instead 馃殌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant