Skip to content

Conversation

@sbouchet
Copy link
Collaborator

What does this PR do?

Upgrade Jest to 29.7.0 in che-remote and remove from che-activity-tracker

What issues does this PR fix?

backport of #610

How to test this PR?

Does this PR contain changes that override default upstream Code-OSS behavior?

  • the PR contains changes in the code folder (you can skip it if your changes are placed in a che extension )
  • the corresponding items were added to the CHANGELOG.md file
  • rules for automatic git rebase were added to the .rebase folder

…cker (che-incubator#610)

* Upgrade Jest to 29.7.0 in che-remote and remove from che-activity-tracker

che-remote:
- Upgraded Jest from 27.3.1 to 29.7.0
- Updated @types/jest from ^27.4.0 to ^29.5.0
- Updated ts-jest from 27.0.7 to 29.4.5
- All tests pass successfully

che-activity-tracker:
- Removed Jest dependencies (jest, @types/jest, ts-jest)
- Removed test script (no tests exist in this extension)
- Removed jsdom overrides (no longer needed without Jest)
- Reduced package count from 283 to 6 packages

This brings che-remote in line with other che extensions using Jest 29.7.0, while removing unnecessary testing infrastructure from che-activity-tracker.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* added typescript as dev dependency, similar to launcher code

---------

Co-authored-by: Claude <noreply@anthropic.com>
@github-actions
Copy link

github-actions bot commented Dec 18, 2025

Click here to review and test in web IDE: Contribute

@sbouchet sbouchet self-assigned this Dec 18, 2025
@sbouchet sbouchet moved this to Unplanned Tasks in Eclipse Che Team C Backlog Dec 18, 2025
@sbouchet sbouchet changed the title Upgrade Jest to 29.7.0 in che-remote and remove from che-activity-tracker [7.113.x] Upgrade Jest to 29.7.0 in che-remote and remove from che-activity-tracker Dec 18, 2025
@github-actions
Copy link

Copy link
Collaborator

@RomanNikitenko RomanNikitenko left a comment

Choose a reason for hiding this comment

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

@sbouchet
thanks for following up #604 (review)

I have a question, my understanding:

  • these changes were required for the main (already merged - thanks!)
  • about a release branch - we usually backport only critical changes - like fix for a bug, CVE and so on

So - is it really required for the release or just nice to have
Any option works for me, just please get an approval from QE if you are going to merge the current PR

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.

3 participants