Open greenkeeper[bot] opened 8 years ago
After pinning to 2.0.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Your tests are passing again with this version. Explicitly upgrade to this version π
The new version differs by 14 commits .
9163439
2.0.2
1191cc5
docs(CHANGELOG): add CHANGELOG for 2.0.2
c5640ef
docs(README): update instrumented code example
c8fce53
chore(espower): update copyright year
f97503f
Merge pull request #35 from power-assert-js/loop-invariants
86a3e4c
test(espower): testing recorder cleanup on expression end
80de58e
test(espower): update expected code
db67946
fix(espower): cleanup captured values on end
d9f0556
test(espower): add failing repro case for recorder in loop
4740400
test(espower): make PowerAssertRecorder testable
74cac77
chore(travis): drop Node v0.12
761cf9f
style(espower): adjust indentation
0b2f295
test(espower): most of instrumentation tests are migrated to file-based fixtures
7663993
chore(package): update espower-location-detector
See the full diff.
Your tests are passing again with this version. Explicitly upgrade to this version π
The new version differs by 19 commits .
ca27989
2.0.3
1706514
docs(CHANGELOG): add CHANGELOG for 2.0.3
9bba08b
Merge pull request #36 from power-assert-js/scope-stack
5e9373f
fix(espower): store scopes in a stack to push/pop them in a consistent way
f0b2db8
test(espower): reproduction case for scope issue on leaving class
9163439
2.0.2
1191cc5
docs(CHANGELOG): add CHANGELOG for 2.0.2
c5640ef
docs(README): update instrumented code example
c8fce53
chore(espower): update copyright year
f97503f
Merge pull request #35 from power-assert-js/loop-invariants
86a3e4c
test(espower): testing recorder cleanup on expression end
80de58e
test(espower): update expected code
db67946
fix(espower): cleanup captured values on end
d9f0556
test(espower): add failing repro case for recorder in loop
4740400
test(espower): make PowerAssertRecorder testable
There are 19 commits in total. See the full diff.
Your tests are passing again with this version. Explicitly upgrade to this version π
The new version differs by 26 commits.
f6cb64a
2.1.0
81a141b
docs: add CHANGELOG for 2.1.0
8f62317
Merge pull request #37 from power-assert-js/escope-options
f574e8e
docs: update result of espower.defaultOptions()
069ab98
refactor: stop using scope.upper to avoid potential unmatch on leaving node
689ecbe
test: more tests on scopes
0e3ec9a
feat: add ecmaVersion
and sourceType
to options
ca27989
2.0.3
1706514
docs(CHANGELOG): add CHANGELOG for 2.0.3
9bba08b
Merge pull request #36 from power-assert-js/scope-stack
5e9373f
fix(espower): store scopes in a stack to push/pop them in a consistent way
f0b2db8
test(espower): reproduction case for scope issue on leaving class
9163439
2.0.2
1191cc5
docs(CHANGELOG): add CHANGELOG for 2.0.2
c5640ef
docs(README): update instrumented code example
There are 26 commits in total.
See the full diff
Version 2.0.1 of espower just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As espower 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 :muscle:
Status Details
- β **ci/circleci** CircleCI is running your tests [Details](https://circleci.com/gh/leecade/fe/69?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link) - β **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/leecade/fe/build/1.0.73)Commits
The new version differs by 5 commits .
6350083
2.0.1
dfe87c3
docs(CHANGELOG): add CHANGELOG for 2.0.1
869ed49
Merge pull request #34 from power-assert-js/arrow-function-with-concise-body
19d2a78
fix(espower): use upper block when assertion is a concise body of ArrowFunctionExpression
02900d5
chore(travis): gulp is installed locally
See the full diff.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: