chore(deps): trivial major-version dependency migrations

[ByronDWall]

Summary

Bumps find-up from 7.0.0 to 8.0.0 (devDependency only).

Included

• find-up: 7.0.0 → 8.0.0 (devDependency). A full-repo grep confirmed the only occurrences of find-up are the package.json version string itself and a mention in .github/renovate.json — there are no source-code imports of find-up anywhere in this repo, and nothing imports pathExists from it. This bump required no call-site code changes, purely a manifest + lockfile update.
  • Upstream breaking changes for v7 → v8, both verified not applicable here:
    1. Requires Node.js >=20 — already satisfied, this repo is on Node 24 per .nvmrc.
    2. No longer re-exports path-exists — consumers must import path-exists directly if they used that re-export. Not used in this repo.

Excluded as not trivial (context for reviewers)

The Dependency Dashboard has several other pending major-version bumps. Each was evaluated and excluded from this PR because it's a framework/tooling migration or otherwise out of scope for a "trivial mechanical bump" PR, not because it's risky in a specific way that was investigated in depth here:

Dependency / group	Reason excluded
actions/checkout, actions/setup-node, pnpm/action-setup (GH Actions majors)	CI tooling major bumps — out of scope per policy
All @commercetools-frontend/* application-kit packages	Framework migration (24.x → 27.x) — out of scope per policy
All babel packages (major)	Framework/build-tooling migration — out of scope per policy
@commitlint/cli, @commitlint/config-conventional, lint-staged (git-workflow-tools major)	See note below — evaluated but not included
All @graphql-codegen/* packages	Code-generation tooling migration — out of scope per policy
All jest packages (major)	Test-framework migration — out of scope per policy
eslint, eslint-formatter-pretty	Linting framework migration — out of scope per policy
@commercetools/platform-sdk (v9)	SDK major migration — out of scope per policy

Flagged for manual review (not blind-included)

@commitlint/cli, @commitlint/config-conventional, and lint-staged were specifically evaluated for this batch and not included. They are git-hook/workflow tooling spanning two majors each, with real config-schema risk (commitlint rule changes, lint-staged config format changes) rather than a purely mechanical version bump. Recommending these go through manual review rather than blind inclusion in a "trivial" batch.

Changeset

No changeset was added. Per CONTRIBUTING.md, "a changeset is not required, as things like documentation or other changes in the repository itself generally don't need a changeset," and PR #1033 (a comparable pure dependency-bump/consolidation PR) included zero changeset files. This PR mirrors that convention: it's a devDependency-only bump with no consumer-facing package version change.

Verification

Ran the full local verification suite in an isolated worktree:

• pnpm typecheck (tsc --noEmit) — pass
• pnpm build (preconstruct build) — pass
• pnpm test (jest) — 535 suites / 1691 tests — pass
• pnpm lint (jest --config jest.eslint.config.js) — 2820 suites — pass

All green, consistent with find-up having zero source-code call sites in this repo.

Notes

• This PR does not merge or close any other PR. It is separate from, and unrelated to, chore(deps): batch-consolidate patch/minor/security Renovate updates #1033 (chore/renovate-batch-consolidation), which was left untouched.

[changeset-bot]

⚠️ No Changeset found

Latest commit: edbeb94

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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