fix: updated jest and @types/jest

[Aryan4884]

What kind of change does this PR introduce?

Bugfix

Issue Number:

Fixes #1942

Did you add tests for your changes?

No

Snapshots/Videos:

N/A

Summary

Upgraded jest and @types/jest version.

Does this PR introduce a breaking change?

No

Have you read the contributing guide?

Yes

Summary by CodeRabbit

• Chores
  • Updated development dependencies for improved testing capabilities, including Jest and its type definitions.

[coderabbitai]

Walkthrough

The pull request updates the package.json file for the talawa-admin project, focusing on upgrading the devDependencies for @types/jest and jest to their latest versions. The @types/jest version is upgraded from ^26.0.24 to ^29.5.14, and the jest version is upgraded from ^27.4.5 to ^29.7.0. Additionally, the resolutions field specifies exact versions for several packages to ensure consistency.

Changes

File	Change Summary
package.json	- Updated @types/jest from ^26.0.24 to ^29.5.14
	- Updated jest from ^27.4.5 to ^29.7.0
	- Resolutions field remains unchanged, ensuring consistency across certain packages.

Assessment against linked issues

Objective	Addressed	Explanation
Upgrade jest and @types/jest to the latest versions, ensuring both dependencies are updated together. (1942)	✅
Address potential issues arising from multiple dependency requirements that may need updating. (1942)	✅
Maintain existing configurations without modifications. (1942)	✅
Ensure that no existing functionality is affected by the upgrade. (1942)	✅
Validate that all tests remain valid and pass successfully after the upgrade. (1942)	❌	No explicit test validation was noted in this PR.

Possibly related issues

• Upgrade @testing-library/jest-dom from 5.16.5 to 6.4.2 #1951: This issue involves upgrading @testing-library/jest-dom, which may require similar updates to testing dependencies.

Possibly related PRs

• eslint-plugin-jest upgraded #2261: This PR updates the eslint-plugin-jest package, which is related to the main PR's updates to Jest and its type definitions in package.json.
• Upgraded @mui/system and peer dependencies #2399: This PR modifies the jest.config.js file, which is relevant to the main PR's updates to the Jest package in package.json.

Suggested reviewers

• palisadoes: Suggested reviewer for expertise in the project and related dependencies.
• varshith257: Another reviewer who may provide insights on the changes made.

Poem

🐰 In the garden of code, we hop and play,
With Jest and types, we brighten the day.
Versions updated, all in a row,
Testing with joy, watch our project grow!
Hops of success, we cheer and we sway,
In the world of dev, it's a splendid ballet! 🌼

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between b81f437 and 24e2088.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• package.json

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

1. The overall code coverage drops below the target threshold of the repository
2. Any file in the pull request has code coverage levels below the repository threshold
3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
2. Read the CONTRIBUTING.md file make

[github-actions]

Congratulations on making your first PR! 🎊 If you haven't already, check out our Contributing Guidelines and PR Reporting Guidelines to ensure that you are following our guidelines for contributing and creating PR.

[palisadoes]

Please fix the failing tests

[palisadoes]

Please fix the failing tests

[palisadoes]

During the week of November 11, 2024 we will start a code freeze on the develop branches in Talawa, Talawa Admin and Talawa-API.

We have completed a project to convert the Talawa-API backend to use PostgreSQL. Work will then begin with us merging code in the develop branches to a new develop-postrgres branch in each repository.

Planning activities for this will be managed in our #talawa-projects slack channel. A GitHub project will be created to track specially labeled issues. We completed a similar exercise last year using a similar methodology.

Starting November 12, California time no new PRs will be accepted against the develop branch. They must be applied to the develop-postrgres branch.

There are some GSoC project features that will need to be merged into develop. These will be the only exceptions.

This activity and the post GSoC 2024 start date was announced in our #general Slack channel last month as a pinned post.

[noman2002]

@Aryan4884 Any update on this one ?

[Cioppolo14]

@Aryan4884 Please fix the conflicting files.

[palisadoes]

We are going to have to close this. We are now using vitest in the repo