chore(deps): update all non-major dependencies

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Type	Update	Change	OpenSSF	Age	Confidence
crate-ci/typos	action	minor	v1.40.1 → v1.47.0
vite (source)	devDependencies	patch	^8.0.0 → ^8.0.2

---

Release Notes

crate-ci/typos (crate-ci/typos)

v1.47.0

Compare Source

v1.46.3

Compare Source

[1.46.3] - 2026-05-23

Fixes

• Don't correct to sequentials
• Don't correct to subdolder

v1.46.2

Compare Source

[1.46.2] - 2026-05-16

Fixes

• Don't correct to criterias
• Don't correct to replaceables

v1.46.1

Compare Source

[1.46.1] - 2026-05-08

Fixes

• Don't correct to confidentials

v1.46.0

Compare Source

[1.46.0] - 2026-04-30

Features

• Updated the dictionary with the April 2026 changes

v1.45.2

Compare Source

[1.45.2] - 2026-04-27

Fixes

• Ignore ssh ed25519 public keys

v1.45.1

Compare Source

Bug Fixes

• Ignore numbers as identifiers (a00831c8)
• Improve the organization of --help (a48a457c)

Features

• Dump files, identifiers, and words (ce365ae1, closes #​41)
• Give control over allowed identifier characters for leading vs rest (107308a6)

Performance

• Use standard identifier rules to avoid doing umber checks (107308a6)
• Only do hex check if digits are in identifiers (68cd36d0)

v1.45.0

Compare Source

Bug Fixes

• Ignore numbers as identifiers (a00831c8)
• Improve the organization of --help (a48a457c)

Features

• Dump files, identifiers, and words (ce365ae1, closes #​41)
• Give control over allowed identifier characters for leading vs rest (107308a6)

Performance

• Use standard identifier rules to avoid doing umber checks (107308a6)
• Only do hex check if digits are in identifiers (68cd36d0)

v1.44.0

Compare Source

Bug Fixes

• Ignore numbers as identifiers (a00831c8)
• Improve the organization of --help (a48a457c)

Features

• Dump files, identifiers, and words (ce365ae1, closes #​41)
• Give control over allowed identifier characters for leading vs rest (107308a6)

Performance

• Use standard identifier rules to avoid doing umber checks (107308a6)
• Only do hex check if digits are in identifiers (68cd36d0)

✂ Note

PR body was truncated to here.

---

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[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

? Verifying lockfile against supply-chain policies (204 entries)...
✗ Lockfile failed supply-chain policy check (204 entries in 5s)
[ERR_PNPM_LOCKFILE_RESOLUTION_VERIFICATION] 34 lockfile entries failed verification:
  @exodus/bytes@1.15.1 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-20T10:53:15.306Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-android-arm-eabi@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:07:03.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-android-arm64@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:06:33.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-darwin-arm64@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:06:27.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-darwin-x64@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:07:50.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-freebsd-x64@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:08:01.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-linux-arm-gnueabihf@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:07:08.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-linux-arm-musleabihf@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:07:13.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-linux-arm64-gnu@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:06:46.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-linux-arm64-musl@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:06:52.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-linux-ppc64-gnu@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:07:25.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-linux-riscv64-gnu@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:07:31.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-linux-riscv64-musl@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:07:36.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-linux-s390x-gnu@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:07:44.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-linux-x64-gnu@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:08:08.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-linux-x64-musl@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:08:14.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-openharmony-arm64@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:06:58.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-win32-arm64-msvc@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:06:40.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-win32-ia32-msvc@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:07:19.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  @oxlint/binding-win32-x64-msvc@1.66.0 [MINIMUM_RELEASE_AGE_VIOLATION] was published at 2026-05-19T08:07:55.000Z, within the minimumReleaseAge cutoff (2026-05-15T14:46:28.344Z)
  …and 14 more

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.