chore: update dependency file-entry-cache to v8

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
file-entry-cache	^6.0.1 -> ^8.0.0

---

Release Notes

jaredwray/file-entry-cache (file-entry-cache)

v8.0.0

Compare Source

Removing support for Nodejs 10, 12, and 14

This is updating modules to the latest versions and supporting Nodejs >=16 moving forward with v8.0.0

What's Changed

• removing support for nodejs 12 and 14 by @​jaredwray in https://github.com/jaredwray/file-entry-cache/pull/43

Full Changelog: jaredwray/file-entry-cache@v7.0.2...v8.0.0

v7.0.2

Compare Source

What's Changed

• removing del module as no longer needed by @​jaredwray in https://github.com/jaredwray/file-entry-cache/pull/40
• upgrading flat-cache to 3.2.0 by @​jaredwray in https://github.com/jaredwray/file-entry-cache/pull/41

Full Changelog: jaredwray/file-entry-cache@v7.0.1...v7.0.2

v7.0.1

Compare Source

What's Changed

• upgrading flat-cache to 3.1.1 by @​jaredwray in https://github.com/jaredwray/file-entry-cache/pull/37
• upgrading chai to 4.3.10 by @​jaredwray in https://github.com/jaredwray/file-entry-cache/pull/38
• upgrading eslint to 8.50.0 and mocha plugin by @​jaredwray in https://github.com/jaredwray/file-entry-cache/pull/39

Full Changelog: jaredwray/file-entry-cache@v7.0.0...v7.0.1

v7.0.0

Compare Source

What's Changed

• upgrading chai and mocha to latest by @​jaredwray in https://github.com/jaredwray/file-entry-cache/pull/32
• removing package-lock and setting tests to nodejs versions by @​jaredwray in https://github.com/jaredwray/file-entry-cache/pull/33
• adding code coverage reporting via codecov by @​jaredwray in https://github.com/jaredwray/file-entry-cache/pull/34
• updating tests for master by @​jaredwray in https://github.com/jaredwray/file-entry-cache/pull/35
• removing support for Nodejs version 10 by @​jaredwray in https://github.com/jaredwray/file-entry-cache/pull/36

Full Changelog: jaredwray/file-entry-cache@v6.0.1...v7.0.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[netlify]

✅ Deploy Preview for docs-eslint ready!

Name	Link
🔨 Latest commit	a9f106f
🔍 Latest deploy log	https://app.netlify.com/sites/docs-eslint/deploys/65b7f3d889adf8000897138f
😎 Deploy Preview	https://deploy-preview-17903--docs-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[nzakas]

I investigated this, and the problem is a couple of transitive dependencies that use the Blue Oak Model License, which is not an OSI approved license, and therefore can't be included in ESLint.

It looks like they have submitted for approval and there will be a vote during January on whether or not to approve this license. So, we will need to wait for that in order to merge this.

[github-actions]

Hi everyone, it looks like we lost track of this pull request. Please review and see what the next steps are. This pull request will auto-close in 7 days without an update.

[nzakas]

Here's the Open JS Foundation tracking issue:
openjs-foundation/cross-project-council#1170

[github-actions]

Hi everyone, it looks like we lost track of this pull request. Please review and see what the next steps are. This pull request will auto-close in 7 days without an update.

[nzakas]

The BlueOak license has been approved, so I updated this PR to allow the license.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.