chore(deps): update dependency chromatic to v18.2.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
chromatic (source)	18.1.0 → 18.2.0

---

Release Notes

chromaui/chromatic-cli (chromatic)

v18.2.0

Compare Source

🚀 Enhancement

• Restore patch build functionality #​1428 (@​jmhobbs)

🐛 Bug Fix

• Upgrade Yarn and set npmMinimalAgeGate to 7 days #​1427 (@​jmhobbs)
• Support more .storybook/main config structures #​1424 (@​codykaup)
• Bound getFileHashes peak memory by concurrency #​1426 (@​codykaup)

Authors: 2

• Cody Kaup (@​codykaup)
• John Hobbs (@​jmhobbs)

---

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Monday through Friday (* * * * 1-5)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

[doistbot]

Straightforward Renovate bump of the chromatic dev dependency from 18.1.0 to 18.2.0 — no breaking changes, just bug fixes and a patch-build enhancement.

Few things worth tightening:

• package-lock.json is out of sync. It still pins chromatic at 18.1.0 while package.json specifies 18.2.0. Run npm install to regenerate the lockfile and commit it, otherwise npm ci in CI will fail with a manifest/lockfile mismatch.

_{Share Feedback • Review Logs}

[doistbot]

The version bump to chromatic@18.2.0 is not reflected in package-lock.json, which still pins chromatic to 18.1.0 (both the root devDependencies entry and node_modules/chromatic). With npm this makes the manifest and lockfile inconsistent, so npm ci (as used in CI) will fail with a package.json/package-lock.json sync error. Run npm install (or otherwise regenerate the lockfile) and commit the updated package-lock.json in this PR.