chore(deps): bump uuid from 8.3.2 to removed in the npm_and_yarn group across 1 directory

[dependabot]

Bumps the npm_and_yarn group with 1 update in the / directory: uuid.

Removes uuid

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[claude]

🔍 Dependency Analysis Summary

⚠️ PR title is misleading. It claims "bump uuid from 8.3.2 to removed", but uuid is not a direct dependency. The actual changes are two top-level package bumps (one major, one minor); uuid is simply no longer pulled in transitively as a side effect.

Actual changes:

Package	Old	New	Bump
@sentry/webpack-plugin	^4.0.2	^5.3.0	Major
cypress (optional)	^15.14.2	^15.15.0	Minor
uuid (transitive)	8.3.2 / 9.0.1	removed	—

Several supporting transitives also changed (@cypress/request 3→4, @sentry/cli 2.50.2→2.58.6, magic-string 0.30.8→0.30.21, @jridgewell/sourcemap-codec 1.5.0→1.5.5, glob 9→13, path-scurry 1→2, minipass 4→7, plus the removal of unplugin and webpack-virtual-modules).

Overall risk: LOW, with one packaging issue that should be addressed before merging — see below.

---

📋 Detailed Changelog Review

@sentry/webpack-plugin 4.0.2 → 5.3.0 (MAJOR)

Source: CHANGELOG

• v5.0.0 breaking changes:
  • Drops support for Node < 18 and webpack < 5 (engines.node: >=18, peerDependencies.webpack: >=5.0.0).
  • Internal: replaced unplugin with native webpack plugin API (removed transitive unplugin, webpack-virtual-modules).
  • Updated minimatch / glob to newer majors.
• v5.2.0: Switched from uuid to native crypto.randomUUID — this is why uuid drops out.
• v5.3.0: New babel auto-inject sentry-label from static text children; vite return-type fix.
• License note: @sentry/cli (and its prebuilt platform binaries) changed from BSD-3-Clause to FSL-1.1-MIT (Functional Source License, converting to MIT after 2 years). The webpack-plugin itself remains MIT. Worth flagging to whoever does license review.

cypress 15.14.2 → 15.15.0 (MINOR, optional dep)

Source: cypress CLI/CHANGELOG.md

• Deprecation: cy.end() is deprecated and will be removed in a future release. ✅ Not used in cypress/ directory.
• Security fixes (transitive):
  • socket.io 4.0.1 → 4.8.3 — addresses GHSA-677m-j7p3-52f9 DoS.
  • uuid 8.3.2 → 11.1.1 internally — addresses SNYK-JS-UUID-16133035.
• Bugfixes: proxy Content-Length: 0 handling, Vite 8 component HMR double-registration, cy.origin race conditions, CSS selector crash on regex-metacharacter attributes, transient Cloud 500 retries, Firefox launch retry, Angular monorepo basename collisions.
• @cypress/request 3 → 4: drops uuid (its engines.node is now >= 14.17.0, fine for Node 24).

---

⚠️ Impact Assessment

Compatibility

Requirement	Project value	OK?
@sentry/webpack-plugin@5 needs Node ≥ 18	runtime is Node 24.x	✅
@sentry/webpack-plugin@5 needs webpack ≥ 5	"webpack": "^5.105.0"	✅
cypress@15.15.0 engine	Node 24.x	✅

Code usage check

• webpack.config.js:1,117 uses only sentryWebpackPlugin({ authToken, org, project, telemetry }). These options are unchanged in v5 — no code changes required.
• cypress.config.ts and cypress/support/* use standard, stable APIs. No cy.end() usage.
• uuid is not imported by any source under assets/, components/chat_widget/src/, or cypress/ — it was purely transitive.

🐛 Lockfile inconsistency (please address before merging)

package-lock.json adds cypress: "15.15.0" to the root dependencies block in addition to optionalDependencies, while package.json only lists it under optionalDependencies:

• package.json:87-89 → optionalDependencies: { cypress: "^15.15.0" }
• package-lock.json:25 → adds "cypress": "15.15.0" to dependencies (no caret, not in package.json)
• package-lock.json:79-81 → also keeps optionalDependencies: { cypress: "^15.15.0" }

This looks like an npm install --save cypress@15.15.0 rather than a managed lockfile refresh. The risk: production installs that skip optionalDependencies may now still pull cypress (and its ~120 MB binary download script) because it appears under regular dependencies in the lock. Recommend regenerating the lockfile cleanly, e.g.:

rm package-lock.json node_modules/.package-lock.json
npm install --include=optional

…and confirming the resulting lock keeps cypress only under optionalDependencies.

---

🛠️ Recommendations

• Action required: Fix the cypress lockfile duplication before merge (see above). After that, the upgrade is safe.
• Testing focus:
  • Production webpack build with sourcemap upload to Sentry — confirm SENTRY_AUTH_TOKEN/SENTRY_ORG/SENTRY_PROJECT flow still works against the sentry-cli 2.58.x binary on the CI runner. The branch in webpack.config.js:113 only fires on GITHUB_REF=refs/heads/main, so this won't exercise on the PR itself.
  • npm run dev and npm run build succeed locally and in CI.
  • One cypress run (npm run cypress:run) to confirm the @cypress/request v4 transition is fine.
• Follow-up tasks:
  • License-review the @sentry/cli switch to FSL-1.1-MIT for the prebuilt CLI binaries if your org tracks third-party licenses.
• Merge recommendation: REVIEW_NEEDED — approve the dep bumps, but fix the lockfile entry for cypress first.

---

📚 Useful Links

• @sentry/webpack-plugin CHANGELOG
• @sentry/webpack-plugin v5.0.0 breaking PR
• Cypress CLI CHANGELOG
• socket.io DoS GHSA-677m-j7p3-52f9
• Functional Source License (FSL)