Open greenkeeper[bot] opened 4 years ago
After pinning to 1.3.26 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
devDependency
@open-wc/testing-karma-bs was updated from 1.3.27
to 1.3.28
.Your tests are passing again with this update. Explicitly upgrade to this version 🚀
The new version differs by 6 commits.
1ad98d8
chore: release new versions
bef5dac
feat(testing-helpers): add waitUntil helper
d6da8d4
fix(es-dev-server): don't join current working directory twice
83587e2
chore: release new versions
bef0d79
chore: formatting
962fc10
fix(testing): add missing files to npm
See the full diff
The devDependency @open-wc/testing-karma-bs was updated from
1.3.26
to1.3.27
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@open-wc/testing-karma-bs 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/jenkins/branch:** This commit cannot be built ([Details](https://jenkins.fcarrascosa.es/job/fcarrascosa-slider/job/greenkeeper%252F@open-wc%252Ftesting-karma-bs-1.3.27/1/display/redirect)).Commits
The new version differs by 4 commits.
e54049f
chore: release new versions
e355027
fix(testing): compatibility with webpack
3f80674
fix: remove unused
path
e3ad027
fix(testing-karma): use an os-agnostic pathResolver
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: