Update dependency ora to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
ora	4.1.1 -> 7.0.1

---

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

---

Release Notes

sindresorhus/ora (ora)

v7.0.1

Compare Source

• Fix missing dependency (#​228) 1dc1ece

v7.0.0

Compare Source

Breaking

• Require Node.js 16 0e96acd

v6.3.1

Compare Source

• Fix Node.js 12 compatibility 4b1c2be

v6.3.0

Compare Source

• Add suffixText option (#​223) 2378eaf

v6.2.0

Compare Source

• Add spinners export to be able to access all available spinners (#​222) f2ac111

v6.1.2

Compare Source

• Revert "Fix preserving stdin's pause state (#​210)" f4e03ea
  • Reason: https://github.com/sindresorhus/ora/issues/211

v6.1.1

Compare Source

• Fix preserving stdin's pause state (#​210) 77ccc1e

v6.1.0

Compare Source

• Expose the spinner interval as a getter 447812b
• Internal refactoring. If you use any undocumented properties, this may break for you.

v6.0.1

Compare Source

• Upgrade dependencies 26ba606

v6.0.0

Compare Source

Breaking

• Require Node.js 12.20 ede1a54
• This package is now pure ESM. Please read this.
• ora.promise is now a named import called oraPromise (#​181) 9c01990
  • import {oraPromise} from 'ora';
• oraPromise now returns the given promise instead of this (#​181) 9c01990
  • This lets you await it directly, which is more useful than chaining.

Improvements

• Improve performance of the .clear() method (#​182) d51c971

v5.4.1

Compare Source

• Fix: Don't allow default as a spinner (#​175) 659f839

v5.4.0

Compare Source

• Improve detection for terminals supporting Unicode c884e0d

v5.3.0

Compare Source

• Use nice spinner on VSCode's terminal and Windows Terminal (#​167) af52bbd

v5.2.0

Compare Source

• Use bl package instead of mute-stream (#​163) 56de27f

v5.1.0

Compare Source

• Add isSilent option (#​155) 1bd812a
• Allow setting prefixText dynamically (#​154) 561bc85

v5.0.0

Compare Source

Breaking

• Require Node.js 10 87010c5

---

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.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

[15:14:22.822] INFO (9): Installing tool node v18.18.0...
v18.18.0
9.8.1
0.19.0
[15:14:25.596] INFO (9): Installed tool node in 2.7s.
[15:14:26.083] INFO (52): Installing tool pnpm v8.8.0...
8.8.0
[15:14:27.626] INFO (52): Installed tool pnpm in 1.5s.
 ERROR  Unexpected number in JSON at position 7388 while parsing '{  "name": "nextjs-project",  "version' in /tmp/worker/e5274f/0e0511/repos/github/X-oss-byte/Canary-nextjs/package.json 

  183 |     "playwright-chromium": "1.38.1",
  184 |     "plop": "3.0.5",
> 185 |  01-30-Add_test_for_issue_45393
      |  ^
  186 |     "postcss-nested": "4.2.3",
  187 |     "postcss-pseudoelements": "5.0.0",
  188 |     "postcss-short-size": "4.0.0",

For help, run: pnpm help install

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: e89c36e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR