[spec] Update graceful-fs: 4.1.15 → 4.2.11 (minor)

[depfu]

👉 This PR is queued up to get rebased by Depfu

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?

✳️ graceful-fs (4.1.15 → 4.2.11) · Repo

Commits

See the full diff on Github. The new version differs by 55 commits:

• 4.2.11
• Add EBUSY to handled error codes for windows directory rename
• update and improve tests somewhat
• 4.2.10
• fix spurious ENOTEMPTY in test on windows ci
• avoid spurious EBUSY in windows CI tests
• ci: output raw tap from test
• actually fix memory leak test failing spuriously
• fix memory leak test failing spuriously
• do not try to patch missing fs functions
• Avoid setPrototypeOf if prototype is undefined
• install with npm 8
• fix: fs.readdir() on ancient nodes that don't know about options
• chore: add copyright year to license
• ci: makework
• 4.2.9
• fix(stat): support throwIfNoEntry for `statSync`
• 4.2.8
• fix: start retrying immediately, stop after 60 seconds
• 4.2.7
• fix: start retrying immediately, stop after 10 attempts
• chore: refactor readdir to be consistent
• Fix copyFile wrapper when retry hits EMFILE again
• Clarify README.md regarding sync methods (#207)
• 4.2.6
• fix: TypeError when loading graceful-fs from worker threads
• fix: copyFile with flags
• run tests in color mode
• 4.2.5
• Avoid hitting __proto__
• Copy over process.chdir.disabled if set
• Support copyFile
• s/travis/GitHub Actions/
• run tests with coverage
• 4.2.4
• fix: attach queue to fs module in addition to global
• 4.2.3
• Split legacy stream properties from regular ones.
• 4.2.2
• Do not inadvertently monkeypatch fs streams
• Hide fs.close and fs.closeSync previous symbols
• Add Node.js 0.x polyfill for global retry queue name
• Create/use global shared retry queue.
• 4.2.1
• Fix `util.promisify` for patched read function
• update deps
• 4.2.0
• push to github with one command, not two
• add node 12 to travis
• Minor code restructuring on fs.stat options
• [email protected]
• Always load graceful-fs BEFORE tap in tests
• update memory leak test for node v12.4
• Add basic test for stat functions with 3 arguments when supported
• Allow stat functions to accept 3 arguments (target, options, cb)

---

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)

[guardrails]

⚠️ We detected 14 security issues in this pull request:

Vulnerable Libraries (14)

Severity	Details
High	pkg:npm/[email protected]@3.0.0 (t) upgrade to: 6.0.1,5.0.1,4.1.1,3.0.1
Critical	pkg:npm/[email protected]@1.0.0 (t) - no patch available
Medium	pkg:npm/[email protected]@6.2.2 (t) - no patch available
High	pkg:npm/[email protected]@0.0.8 (t) - no patch available
High	pkg:npm/[email protected]@3.0.4 (t) upgrade to: 3.0.5
Critical	pkg:npm/[email protected]@0.2.3 (t) upgrade to: 0.4.0
N/A	pkg:npm/[email protected]@2.6.9 (t) upgrade to: 3.1.0
Medium	pkg:npm/[email protected]@5.2.0 (t) - no patch available
Medium	pkg:npm/[email protected]@6.10.2 (t) upgrade to: 6.12.3
High	pkg:npm/[email protected]@0.0.10 (t) - no patch available
Medium	pkg:npm/[email protected]@2.88.0 (t) - no patch available
High	pkg:npm/[email protected]@11.1.1 (t) - no patch available
High	pkg:npm/[email protected]@1.1.0 (t) upgrade to: 1.1.1
High	pkg:npm/[email protected]@4.0.0 (t) upgrade to: 3.2.2,4.0.1,5.0.5

More info on how to fix Vulnerable Libraries in JavaScript.

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.