fix(deps): update dependency hasha to v7

[renovate]

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package	Change	Age	Confidence
hasha	^6.0.0 -> ^7.0.0

---

Release Notes

sindresorhus/hasha (hasha)

v7.0.0

Compare Source

Breaking

• Require Node.js 20 75a0ef0

Improvements

• Add signal option 48a9073
• Improve performance a2c5caa

---

---

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 was generated by Mend Renovate. View the repository job log.

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to d76f7d7 in 54 seconds. Click for details.

• Reviewed 13 lines of code in 1 files
• Skipped 1 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. package.json:26

• Draft comment:
  The updated hasha now requires Node.js 20. Consider adding an 'engines' field to package.json or otherwise ensuring that the runtime supports Node 20, as this might break GitHub Actions environments running on older Node versions.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 20% vs. threshold = 50% Since this is a GitHub Action, Node.js version compatibility is important. However, the presence of @types/node 20.x in devDependencies suggests the project is already targeting Node 20. The comment seems speculative ("might break") rather than definitive. Also, GitHub Actions now defaults to Node 20 as of November 2023. I might be wrong about the Node.js version being already handled - devDependencies don't necessarily reflect runtime requirements. The comment could be raising a valid concern about explicit version requirements. While true, GitHub Actions now defaults to Node 20, and the project appears to be already developed against Node 20. The comment is speculative and suggests adding optional configuration rather than fixing a definite issue. Delete the comment. It's speculative, suggests optional configuration rather than fixing a clear issue, and the project already appears to target Node 20.

Workflow ID: wflow_59OuCvYbrHWoNgoz

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}