auru/unity-cache

Cache abstraction around localforage

unity-cache's Issues

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

Version 2.6.0 of rimraf just got published.

Branch	Build failing 🚨
Dependency	rimraf
Current Version	2.5.4
Type	devDependency

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

As rimraf 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

• ❌ dependency-ci Failed dependency checks Details

Commits

The new version differs by 5 commits .

• 5b661e4 v2.6.0
• c09915f update tap
• d53235d Make rimraf.sync 10000% more reliable on Windows
• e8b10a7 Retry on EBUSY et al on non-windows platforms as well
• 0fac5f7 Add --no-glob option to cli

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-config-unity is breaking the build 🚨

Version 1.0.1 of eslint-config-unity just got published.

Branch	Build failing 🚨
Dependency	eslint-config-unity
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 eslint-config-unity 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

• ✅ dependency-ci Dependencies checked Details

• ❌ ci/circleci Your tests failed on CircleCI 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 commitizen is breaking the build 🚨

Version 2.9.6 of commitizen just got published.

Branch	Build failing 🚨
Dependency	commitizen
Current Version	2.9.5
Type	devDependency

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

As commitizen 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

• ❌ dependency-ci Failed dependency checks Details

Release Notes

v2.9.6

2.9.6 (2017-02-16)

Bug Fixes

• bump vulnerable dependency (#421) (2a101b86)

Commits

The new version differs by 2 commits .

• 2a101b8 fix: bump vulnerable dependency (#421)
• b17eecb docs(readme): link to contributing (#419)

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 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

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 fake-indexeddb is breaking the build 🚨

Version 1.0.9 of fake-indexeddb just got published.

Branch	Build failing 🚨
Dependency	fake-indexeddb
Current Version	1.0.8
Type	devDependency

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

As fake-indexeddb 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

• ❌ dependency-ci Failed dependency checks Details

Commits

The new version differs by 6 commits .

• 2715fa9 1.0.9
• 0e03a58 Merge branch 'master' of https://github.com/dumbmatter/fakeIndexedDB
• 9ece48c Remove shrinkwrap, since this is a library. Hopefully nothing will break
• 1757f4b Correctly handle indexes for records that do not have key properties - fixes #15
• b9706c7 Merge pull request #13 from ai/patch-1
• f5bbb7c Add syntax highlight to docs

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 browser-env is breaking the build 🚨

Version 2.0.20 of browser-env just got published.

Branch	Build failing 🚨
Dependency	browser-env
Current Version	2.0.19
Type	devDependency

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

As browser-env 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

• ❌ dependency-ci Failed dependency checks Details

Commits

The new version differs by 4 commits .

• 3e5e9b9 2.0.20
• ac13707 fix(package): update jsdom to version 9.10.0 (#32)
• 8569dd3 chore(package): update ava to version 0.18.0
• a36ec73 Change npm badge to show monthly downloads

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 coveralls is breaking the build 🚨

Version 2.11.16 of coveralls just got published.

Branch	Build failing 🚨
Dependency	coveralls
Current Version	2.11.15
Type	devDependency

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

As coveralls 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

• ❌ dependency-ci Failed dependency checks Details

Commits

The new version differs by 13 commits .

• 8dfcfd6 version bump
• 4bc93ac Merge branch 'master' of github.com:nickmerwin/node-coveralls
• 671acca removed codeship badge
• f390392 Merge pull request #152 from ndaidong/master
• de968b0 Merge pull request #147 from hyperlink/update-request-dep
• 72a4046 Merge pull request #154 from a0viedo/patch-1
• 87b27f7 Merge pull request #142 from Hirse/feature/travis-pr
• 3edbecb Merge pull request #155 from kasperlewau/master
• d117e3d reenable drone
• dd230f6 don't hardcode minor version
• cc0882d Update outdate dependencies
• 99edf1a Fix node-uuid deprecation by updating request dependency
• f94b647 Get PR number from TRAVIS

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 🌴

Missing docs

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

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 1.3.16 of conventional-changelog-cli was just published.

Branch	Build failing 🚨
Dependency	conventional-changelog-cli
Current Version	1.3.15
Type	devDependency

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

conventional-changelog-cli 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

• ❌ Tidelift An error occured Details

---

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 ava is breaking the build 🚨

Version 0.18.2 of ava just got published.

Branch	Build failing 🚨
Dependency	ava
Current Version	0.18.1
Type	devDependency

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

As ava 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

• ❌ dependency-ci Failed dependency checks Details

Release Notes

0.18.2

Many bug fixes for snapshot testing, magic assert, and the type definitions: v0.18.1...v0.18.2

Commits

The new version differs by 26 commits .

• 98dded5 0.18.2
• 7cba283 Speed up flow check (#1241)
• d47c5c8 Document that deepEqual() uses lodash.isequal
• 2ff56ce Don't call toJSON() when formatting values
• 795f097 @ava/pretty-format@^1.1.0
• 9cea60d Ensure test run failures crash worker (#1265)
• f3b60f4 Code excerpt fixes (#1271)
• 8d6f9bc Fix typo in babelrc docs
• 3d75834 Remove Notes section from babelrc documentation
• 4f87059 Ensure watcher rethrows logger errors
• da68f29 Simplify failure output - fixes #1072 (#1234)
• 2c683b9 Clean up API tests (#1258)
• 8a8669c Generate HTML coverage reports (#1259)
• 87ea70f Ensure TAP reporter test does not write to stderr (#1240)
• 09a4765 Avoid helper compilation during API tests

There are 26 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 babel-core is breaking the build 🚨

Version 6.23.0 of babel-core just got published.

Branch	Build failing 🚨
Dependency	babel-core
Current Version	6.22.1
Type	devDependency

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

As babel-core 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

• ❌ dependency-ci Failed dependency checks 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 🌴