Closed brisberg closed 4 years ago
Thanks for finding and fixing the problem!
Do you mind doing another release? (or at least just a tag).
I'd feel better updating my dependency to a locked version than to master
itself where it might pull in future commits without warning.
:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Fails when using the latest version of Jest (26.1.0).
Jest now access a few internal calls on mocked functions which trigger the "unmocked properties" safe guard.
Interesting issue with reproducing this with your test cases. Pulling the repo and upgrading to Jest 26 still causes all the tests to pass. However, if you
SKIP
the test aboutmockGlobal
whereallowUndefined
is true, the other tests fail with the above errors.I am guessing that something is not being cleaned up correctly between cases, as those tests should be independent.