chore(deps): update dependency xo to ^0.61.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
xo	^0.60.0 → ^0.61.0

---

Release Notes

xojs/xo (xo)

v0.61.1

Compare Source

v0.61.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

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

[polylane]

Warning

Polylane could not verify the production impact of this pull request.

Re-checked head 667d9b0 against prior head 5c56020: the inter-head diff is lockfile-only (patch bumps to dev-track packages browserslist, prettier, baseline-browser-mapping, electron-to-chromium), package.json byte-identical; xo stays a devDependency no workflow or the Parcel build executes, and no attached account deploys this extension.

View the full analysis →

Failure trajectories: none plausible. 2 failure modes were considered and refuted against observed production traffic.

Refuted trajectories (2): what was ruled out, and why

• Lockfile churn alters a production runtime dependency: Every changed lockfile entry carries dev:true and belongs to the xo devDependency tree; the runtime dependencies section of package-lock.json and package.json is untouched, so nothing the extension bundle imports changes
• CI or build path executes the bumped xo against production code: No CI job invokes xo and no account-scoped resource runs or deploys this extension; the only executable path (parcel build) does not consume devDependencies linters

Dependency changes

Package	Change	Jump	Release age
@emnapi/core (lockfile)	added 1.10.0	—	—
@emnapi/runtime (lockfile)	added 1.10.0	—	—
@emnapi/wasi-threads (lockfile)	added 1.2.1	—	—
@eslint-community/eslint-plugin-eslint-comments (lockfile)	added 4.8.1	—	—
@eslint-community/eslint-utils (lockfile)	4.4.1 → 4.10.1	minor	—
@eslint-community/regexpp (lockfile)	4.12.1 → 4.12.2	patch	—
@eslint/config-array (lockfile)	added 0.21.2	—	—
@eslint/config-helpers (lockfile)	added 0.4.2	—	—
@eslint/core (lockfile)	added 0.17.0	—	—
@eslint/eslintrc (lockfile)	3.2.0 → 3.3.7	minor	—
@eslint/object-schema (lockfile)	added 2.1.7	—	—
@eslint/plugin-kit (lockfile)	added 0.4.1	—	—
@humanfs/core (lockfile)	added 0.19.2	—	—
@humanfs/node (lockfile)	added 0.16.8	—	—
@humanfs/types (lockfile)	added 0.15.0	—	—
@humanwhocodes/retry (lockfile)	added 0.4.3	—	—
@jridgewell/gen-mapping (lockfile)	removed (was 0.3.8)	—	—
@jridgewell/resolve-uri (lockfile)	removed (was 3.1.2)	—	—
@jridgewell/set-array (lockfile)	removed (was 1.2.1)	—	—
@jridgewell/source-map (lockfile)	removed (was 0.3.6)	—	—
@jridgewell/sourcemap-codec (lockfile)	removed (was 1.5.0)	—	—
@jridgewell/trace-mapping (lockfile)	removed (was 0.3.25)	—	—
@napi-rs/wasm-runtime (lockfile)	added 1.2.4	—	—
@pkgr/core (lockfile)	0.1.1 → 0.3.6	minor	—
@rtsao/scc (lockfile)	removed (was 1.1.0)	—	—

_{…and 251 more dependency changes not shown.}

Analysed against 4 cloud accounts and 1 repository

• Cloud accounts: SoferAI, soferai, Sofer.Ai, SoferAI
• Repository: SoferAi/web-extension

Polylane could not find the cloud resources this repository manages, so this review looked at the entire cloud account. Connect this repository to its resources and the next review will focus on exactly what this code deploys to.

_{Polylane analysed 667d9b0 for production impact. You can ask follow-ups by mentioning @polylane in a comment.}

Did this help? React 👍 or 👎 so the next review is sharper.