Skip to content

Upgrade Deps#72

Open
HappyPaul55 wants to merge 2 commits into
mainfrom
upgrade-deps-2026-07-01
Open

Upgrade Deps#72
HappyPaul55 wants to merge 2 commits into
mainfrom
upgrade-deps-2026-07-01

Conversation

@HappyPaul55

@HappyPaul55 HappyPaul55 commented Jan 7, 2026

Copy link
Copy Markdown
Contributor

This pull request updates several dependencies and devDependencies in the package.json file to their latest patch or minor versions. These upgrades help ensure compatibility, security, and access to the latest features and bug fixes.

Dependency updates:

  • Upgraded core dependencies including @deskpro/deskpro-ui, @sentry/react, @sentry/vite-plugin, @types/lodash, react-router-dom, semver, and simplebar to newer versions for improved stability and features. [1] [2]

DevDependency updates:

  • Updated devDependencies such as @babel/traverse, @testing-library/jest-dom, @types/react, @types/semver, jest-environment-jsdom, styled-components, ts-jest, typescript, and vite to keep the development environment current and reduce potential issues with outdated tooling. [1] [2]

Summary by Sourcery

Update application and tooling dependencies to newer patch and minor versions to keep the project aligned with the current ecosystem.

Build:

  • Bump runtime dependencies (UI library, Sentry, routing, utility libraries) to their latest compatible versions.
  • Refresh devDependencies for testing, TypeScript, styling, and build tooling (including Jest, TypeScript, and Vite) to newer patch releases.

@HappyPaul55
HappyPaul55 requested a review from Copilot January 7, 2026 14:06
@sourcery-ai

sourcery-ai Bot commented Jan 7, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates application and tooling dependencies in package.json (and corresponding versions in pnpm-lock.yaml) to newer patch/minor releases to keep the runtime and build/test toolchain current.

File-Level Changes

Change Details Files
Bump runtime dependencies to newer patch/minor versions.
  • Update @deskpro/deskpro-ui to ^8.4.0
  • Update @sentry/react to ^9.47.1 and @sentry/vite-plugin to ^3.6.1
  • Update @types/lodash to ^4.17.21
  • Update react-router-dom to ^7.11.0
  • Update semver to ^7.7.3 and simplebar to ^6.3.3
package.json
pnpm-lock.yaml
Bump devDependencies for build, test, and type tooling.
  • Update @babel/traverse to ^7.28.5 and @testing-library/jest-dom to ^6.9.1
  • Update React and semver type definitions to latest 17.x/7.x patches
  • Update jest-environment-jsdom to ^30.2.0
  • Update styled-components, ts-jest, typescript, and vite to newer patch/minor versions
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

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

  • Consider keeping jest-environment-jsdom aligned with the major version of jest (currently 29.7.0 vs 30.2.0) to avoid subtle test runner incompatibilities; upgrading jest as well or pinning jest-environment-jsdom to a 29.x version would make this more consistent.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Consider keeping `jest-environment-jsdom` aligned with the major version of `jest` (currently 29.7.0 vs 30.2.0) to avoid subtle test runner incompatibilities; upgrading `jest` as well or pinning `jest-environment-jsdom` to a 29.x version would make this more consistent.

## Individual Comments

### Comment 1
<location> `package.json:58` </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.5.0",
</code_context>

<issue_to_address>
**issue (bug_risk):** Jest core and jest-environment-jsdom major versions are out of sync.

`jest` is still on 29.x (`"jest": "^29.7.0"`), but `jest-environment-jsdom` is now 30.x. Jest environments are expected to match Jest’s major version, and mixing 29/30 can cause subtle runtime issues. Please either keep `jest-environment-jsdom` on a 29.x-compatible version or upgrade `jest` to 30.x in the same change so they stay aligned.
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment thread package.json
"eslint-plugin-react-hooks": "4.3.0",
"jest": "^29.7.0",
"jest-environment-jsdom": "^30.0.5",
"jest-environment-jsdom": "^30.2.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue (bug_risk): Jest core and jest-environment-jsdom major versions are out of sync.

jest is still on 29.x ("jest": "^29.7.0"), but jest-environment-jsdom is now 30.x. Jest environments are expected to match Jest’s major version, and mixing 29/30 can cause subtle runtime issues. Please either keep jest-environment-jsdom on a 29.x-compatible version or upgrade jest to 30.x in the same change so they stay aligned.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates multiple dependencies and devDependencies to their latest patch or minor versions to improve stability, security, and access to bug fixes.

Key changes:

  • Core dependencies upgraded including @deskpro/deskpro-ui (8.3.1→8.4.0), @sentry/react (9.38.0→9.47.1), and react-router-dom (7.6.3→7.11.0)
  • Development tooling updated including typescript (5.8.3→5.9.3), vite (6.3.6→6.4.1), and various testing libraries
  • Lock file updated with corresponding transitive dependency changes

Reviewed changes

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

File Description
package.json Updates 7 core dependencies and 9 devDependencies to newer minor/patch versions
pnpm-lock.yaml Reflects package.json changes with updated dependency resolution tree and version pins

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

@github-actions

github-actions Bot commented Jan 7, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants