Upgrade Deps

[HappyPaul55]

This pull request updates several dependencies and devDependencies in the package.json file to their latest versions. These upgrades primarily focus on keeping the project up to date with security patches, bug fixes, and new features.

Dependency updates:

• Upgraded core dependencies including @deskpro/deskpro-ui, @sentry/react, @sentry/vite-plugin, @tanstack/react-query, and react-router-dom to their latest versions.

Development tooling updates:

• Updated development dependencies such as @swc/core, @types/react, jest-environment-jsdom, styled-components, typescript, and vite to newer versions for improved performance and compatibility.

Summary by Sourcery

Update application and tooling dependencies to newer versions to keep the project current and compatible with the surrounding ecosystem.

Build:

• Bump core runtime dependencies including UI, error reporting, data fetching, and routing libraries to more recent versions in package.json.
• Upgrade build, TypeScript, styling, and test-related devDependencies (including Vite, TypeScript, SWC, Jest environment, and styled-components) to newer versions.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Update runtime and development dependencies in package.json and pnpm-lock.yaml to newer minor/patch versions to keep the app, build, and test tooling current and compatible.

File-Level Changes

Change	Details	Files
Bump core application and tooling dependencies to newer minor/patch releases.	Update UI, Sentry, React Query, and React Router runtime packages to newer compatible versions in package.json. Update build and testing-related devDependencies including SWC, React type definitions, Jest jsdom environment, styled-components, TypeScript, and Vite to newer versions in package.json. Refresh pnpm-lock.yaml to align with the new dependency versions and resolve transitive updates.	package.json pnpm-lock.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• Consider aligning the jest-environment-jsdom major version with jest (currently Jest 29 vs jsdom env 30), as mixing major versions can lead to subtle runtime or config incompatibilities.
• Given the upgrade to TypeScript 5.9.3, double-check that the existing ts-jest version (27.1.5) still officially supports this TS/Jest combo, as older ts-jest releases often lag behind newer TypeScript and Jest versions.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider aligning the `jest-environment-jsdom` major version with `jest` (currently Jest 29 vs jsdom env 30), as mixing major versions can lead to subtle runtime or config incompatibilities.
- Given the upgrade to TypeScript 5.9.3, double-check that the existing `ts-jest` version (27.1.5) still officially supports this TS/Jest combo, as older `ts-jest` releases often lag behind newer TypeScript and Jest versions.

## Individual Comments

### Comment 1
<location> `package.json:50` </location>
<code_context>
     "eslint-plugin-react-hooks": "4.3.0",
     "jest": "^29.7.0",
-    "jest-environment-jsdom": "^30.0.5",
+    "jest-environment-jsdom": "^30.2.0",
     "prettier": "^2.8.8",
     "rollup-plugin-copy": "3.4.0",
</code_context>

<issue_to_address>
**issue (bug_risk):** The `jest-environment-jsdom` v30 range may not be compatible with Jest 29.x.

Since `jest-environment-jsdom` is usually versioned in sync with Jest, mixing 29.x Jest with a 30.x environment risks subtle test runtime or API incompatibilities. Consider either pinning `jest-environment-jsdom` to a 29.x range or upgrading Jest and related packages to 30.x together.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Copilot]

Pull request overview

This PR upgrades several production dependencies and development tooling packages to their latest minor/patch versions. The changes focus on keeping the project current with security patches, bug fixes, and feature updates across core libraries, monitoring tools, and development dependencies.

Key changes:

• Core UI library and React ecosystem packages updated to latest versions
• Sentry monitoring tools upgraded for improved error tracking
• Development tooling (TypeScript, Vite, Jest, SWC) updated to newer versions

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File	Description
package.json	Updates version specifiers for 13 dependencies including core UI, Sentry, React Query, build tools, and type definitions
pnpm-lock.yaml	Comprehensive lockfile update reflecting all transitive dependency changes from the package.json updates

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

Build for commit 1e0bfc4 deployed to: https://surveymonkey-pr-56.ci.next.deskprodemo.com

URLs:
https://surveymonkey-pr-56.ci.next.deskprodemo.com/horizon-ui/app