Open greenkeeper[bot] opened 6 years ago
After pinning to 0.1.10 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
dependency
reflect-metadata was updated from 0.1.12
to 0.1.13
.Your tests are still failing with this version. Compare changes
Version 0.1.12 of reflect-metadata was just published.
This version is covered by your current version range and after updating it in your project the build failed.
reflect-metadata is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
- ✅ **dependency-ci** Dependencies checked [Details](https://dependencyci.com/builds/389805) - ❌ **semaphoreci** The build failed on Semaphore. [Details](https://semaphoreci.com/latticework/jali/branches/greenkeeper-reflect-metadata-0-1-12/builds/1)Release Notes
reflect-metadata v0.1.12This release contains some bug fixes and test improvements. It addresses the following issues:
This release also fixes a critical issue in 0.1.11 that prevents the library from loading.
Commits
The new version differs by 4 commits.
c775af7
Fix issue with exporter
69f4359
Do not clobber existing Reflect metadata polyfill. Fixes #80, #78
d20867e
Fix npmignore.
c9451f3
Drop legacy 'licenses' field, update bower.json
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: