test: [Automatic] Constraints upgrades: ipython, napari, sentry-sdk, superqt, vispy

[github-actions]

This PR is automatically created and updated by PartSeg GitHub
action cron to keep bundle dependencies modules up to date.

The updated packages are:

• app-model
• asttokens
• build
• certifi
• charset-normalizer
• click
• coverage
• dask
• debugpy
• fsspec
• idna
• ipython
• jupyter-client
• napari
• npe2
• pillow
• pydantic-settings
• pyinstaller
• pyinstaller-hooks-contrib
• pytest
• python-dotenv
• rpds-py
• sentry-sdk
• setuptools
• superqt
• tornado
• tqdm
• traitlets
• typer
• typing-extensions
• vispy
• wcwidth
• wrapt

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates pinned dependency versions across multiple Python-version-specific constraints files, primarily upgrading ipython and several related packages in the test/bundle environment.

File-Level Changes

Change	Details	Files
Update pinned dependency versions in Python-version-specific constraints files for ipython and related packages.	Bump ipython to a newer compatible version across all constraints files (including pydantic_1 and docs variants). Synchronize versions of related tooling dependencies (debugpy, idna, jupyter-client, snowballstemmer, tqdm, traitlets, typer, wcwidth) across all Python 3.10–3.14 constraints files. Ensure consistency of constraints between standard and pydantic_1 constraint sets for each Python version.	requirements/constraints_py3.10.txt requirements/constraints_py3.10_pydantic_1.txt requirements/constraints_py3.11.txt requirements/constraints_py3.11_pydantic_1.txt requirements/constraints_py3.12.txt requirements/constraints_py3.12_docs.txt requirements/constraints_py3.12_pydantic_1.txt requirements/constraints_py3.13.txt requirements/constraints_py3.13_pydantic_1.txt requirements/constraints_py3.14.txt requirements/constraints_py3.14_pydantic_1.txt

---

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 left some high level feedback:

• Given that the same dependency set is pinned separately for each Python version/pydantic combo, consider factoring shared constraints into a common base file to reduce duplication and the risk of version skew between these constraint files.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Given that the same dependency set is pinned separately for each Python version/pydantic combo, consider factoring shared constraints into a common base file to reduce duplication and the risk of version skew between these constraint files.

---

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.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.56%. Comparing base (2d4781f) to head (98c1ffa).
⚠️ Report is 2 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #1409      +/-   ##
===========================================
- Coverage    92.58%   92.56%   -0.02%     
===========================================
  Files          211      211              
  Lines        33224    33224              
===========================================
- Hits         30759    30755       -4     
- Misses        2465     2469       +4     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud