Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ unexpected (^12.0.0 → ^13.0.0) · Repo · Changelog
Release Notes
13.0.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 27 commits:
13.0.0
Add release notes
Merge pull request #820 from unexpectedjs/depfu/update/npm/eslint-plugin-markdown-2.2.1
Adjust configuration based on https://github.com/eslint/eslint-plugin-markdown#advanced-configuration
Apply the jasmine patch for 4.x as well
Expect jasmine to exit with 3 when tests have failed
Update jasmine to ^4.1.0
Drop support for node.js 10 and 12, add 16
Merge pull request #847 from unexpectedjs/depfu/update/npm/jasmine-3.99.0
Merge pull request #851 from unexpectedjs/feature/inspectAsBigintLiteral
Merge pull request #782 from unexpectedjs/chore/removeLegacyTypelessAddAssertion
Merge pull request #781 from unexpectedjs/feature/preventSatisfyAgainstNonPlainObject
Throw if the user attempts to install unexpected-set
prettier --write lib/assertions.js
Merge branch 'feature/absorbUnexpectedSet'
Merge pull request #785 from unexpectedjs/feature/childInheritsFromParentExpect
Fix tests
Inspect BigInts as 123n instead of BigInt(123)
Prevent test from bleeding into the global expect
Hmm, why shouldn't child expects made before installing a hook be affected, really?
Make a child expect's prototype chain include the parent expect
Try to bump karma's timeouts to see if that helps with the flaky browser test action
Update eslint-plugin-markdown to version 2.2.1
eslint --fix .
npm i --save-dev eslint-plugin-n eslint-config-standard@latest && npm uninstall eslint-plugin-node eslint-plugin-standard
Merge remote-tracking branch 'origin/depfu/update/npm/eslint-plugin-promise-6.0.0'
Update karma to ^6.3.16
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands