fix(deps): update dependency execa to v8

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
execa	^7.0.0 -> ^8.0.0

---

Release Notes

sindresorhus/execa (execa)

v8.0.1

Compare Source

Fixes

• Fix and document support for the {encoding: 'buffer'} option. It is the same as {encoding: null}, but preferred over it. (#​572)

v8.0.0

Compare Source

Breaking

• Require Node.js 16.7.0 and later (#​569)

---

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.

[travi]

this doesnt fit with the currently supported engines definition for node. unlike most of the packages in the org, we've been more open to supporting lower node versions with this package because we know there are consumers outside of the org.

since this would be a breaking change and node v16 will be EOL in just a few months, i dont think we should change our minimum required node version without dropping v16 completely. since the EOL date is coming up, i think we should just wait for that date and realese a major version at that point. i could be convinced to jut go ahead and drop v16 now, but i dont think we need to rush.

[gr2m]

since this would be a breaking change and node v16 will be EOL in just a few months, i dont think we should change our minimum required node version without dropping v16 completely. since the EOL date is coming up, i think we should just wait for that date and realese a major version at that point. i could be convinced to jut go ahead and drop v16 now, but i dont think we need to rush.

I agree, let's wait, and then drop Node 16 entirely.

[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.

[github-actions]

🎉 This PR is included in version 10.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀