This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
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)
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ tape (5.3.1 → 5.5.2) · Repo
Commits
See the full diff on Github. The new version differs by 51 commits:
v5.5.2
[Dev Deps] update `@ljharb/eslint-config`; pin `eslint`
[Deps] unpin `minimatch`
v5.5.1
[Fix] pin `minimatch` to v3.0.4, due to a breaking change in v3.0.5
v5.5.0
Merge tag 'v4.15.0'
v4.15.0
[Dev Deps] update `eslint`
[New] add `--no-only` flag/`NODE_TAPE_NO_ONLY_TEST` (#572)
[Tests] handle a broken error `cause` in node 16.9/16.10
[New] add `--no-only` flag/`NODE_TAPE_NO_ONLY_TEST`
[Tests] handle a broken error `cause` in node 16.9/16.10
[meta] fix `prelint` so it does not fail outside of a git repo
[meta] fix `prelint` so it does not fail outside of a git repo
v5.4.1
[Robustness] use cached `.test`
[Robustness] use cached `.test`
[Fix] avoid failing in ES3 engines that lack `Object.keys`, and `.every`
[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`
[meta] better `eccheck` command
v5.4.0
[Deps] update `has-dynamic-import`, `object-inspect`
[Dev Deps] update `eslint`, `@ljharb/eslint-config`
[New] `t.match`/`t.doesNotMatch: fail the test instead of throw on wrong input types.
[actions] reuse common workflows
[New] `t.match`/`t.doesNotMatch: fail the test instead of throw on wrong input types.
[actions] reuse common workflows
[Dev Deps] update `eslint`, `@ljharb/eslint-config`
v5.3.2
[Tests] handle carriage returns in stack traces on Windows
[readme] hard wraps bad, soft wraps good
[meta] better `eccheck` command
[Tests] handle carriage returns in stack traces on Windows
[readme] hard wraps bad, soft wraps good
[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `safe-publish-latest`
[Fix] use `file://` URLs for dynamic `import()`
[Tests] node 17+ smooshes a version number on the end of the stack trace
[actions] update codecov uploader
[Deps] update `string.prototype.trim`
[Dev Deps] update `array.prototype.flatmap`
Revert "[Dev Deps] ping `signal-exit` to v3.0.3 due to https://github.com/tapjs/signal-exit/issues/66"
[readme] fix markdown; github still has a rendering bug
[Dev Deps] ping `signal-exit` to v3.0.3 due to https://github.com/tapjs/signal-exit/issues/66
[readme] add badges
[Deps] update `glob`
[meta] Exclude `fs` from browser bundles (#565)
[Deps] update `object-inspect`, `resolve`
[meta] Exclude `fs` from browser bundles
[Dev Deps] update `@ljharb/eslint-config`
[Tests] handle v8 6.9 changing an error message
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