chore(deps): upgrade typescript from 5.6.2 to 5.6.3

[CHIRANTH-24]

What kind of change does this PR introduce?

Issue Number:

Fixes #2334

Did you add tests for your changes?

No

Snapshots/Videos:

None

If relevant, did you update the documentation?

No

Summary

This PR upgrades TypeScript from version 5.6.2 to 5.6.3.

Does this PR introduce a breaking change?

Other information

Have you read the contributing guide?

Yes

Summary by CodeRabbit

• Chores
  • Updated the TypeScript dependency to version 5.6.3, which may include bug fixes and improvements.

[coderabbitai]

Walkthrough

The pull request involves a minor update to the package.json file for the talawa-admin project, specifically upgrading the typescript dependency from version 5.6.2 to 5.6.3. This change reflects an update to the TypeScript library, indicating potential bug fixes or improvements. No other dependencies or configurations within the package.json file have been modified.

Changes

File	Change Summary
package.json	Updated typescript dependency from ^5.6.2 to ^5.6.3

Assessment against linked issues

Objective	Addressed	Explanation
Upgrade package typescript from 5.6.2 to 5.6.3 (#2334)	✅

Possibly related issues

• Upgrade package typescript from 4.9.5 to 5.5.4 #2255: The change addresses the objective to upgrade TypeScript, which is directly relevant to the current PR.
• Upgrade package typescript from 4.9.5 to 5.4.5 #2016: The PR's objective to fix previous test failures during TypeScript upgrades aligns with the ongoing efforts in this update.
• Upgrade package eslint-plugin-tsdoc from 0.2.17 to 0.3.0 #2136: While this issue focuses on a different package, the general theme of upgrading dependencies is relevant.
• Upgrade jest and @types/jest #1942: This issue discusses upgrading dependencies and ensuring no configurations are altered, which is indirectly related to the current PR.

Possibly related PRs

• eslint-plugin-jest upgraded #2261: This PR updates several TypeScript-related dependencies, directly related to the TypeScript version bump in the current PR.
• fixed the eslint checker #2318: This PR modifies the lint:check script, which may have indirect implications for TypeScript linting processes.

Poem

🐰 In the garden of code, a change so spry,
With TypeScript's bump, we reach for the sky.
A version upgraded, just a small hop,
Fixing the bugs, we won't let them stop!
In the world of dependencies, we dance and we play,
Thank you, dear TypeScript, for brightening our day! 🌼

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 025bc1d and c397571.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• package.json (1 hunks)

🧰 Additional context used

🔇 Additional comments (1)

package.json (1)

61-61: LGTM: TypeScript dependency updated as intended.

The update of the TypeScript dependency from ^5.6.2 to ^5.6.3 aligns with the PR objectives. This minor version update is likely to include bug fixes and small improvements.

To ensure compatibility with the project, please run the following verification steps:

---

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.

[varshith257]

@CHIRANTH-24 You need to create a local branch and raise PR for develop

[CHIRANTH-24]

@varshith257
Should I create a branch with name other than "develop"?

[varshith257]

Yes

…

On Fri, 18 Oct, 2024, 12:30 am CHIRANTH RAJU C, ***@***.***> wrote: @varshith257 <https://github.com/varshith257> Should I create a branch with name other than "develop"? — Reply to this email directly, view it on GitHub <#2336 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4BF3HF6DPWA2JW6NLSUGEDZ4ACLDAVCNFSM6AAAAABQC33FCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRQGMYTEOBUGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[CHIRANTH-24]

@varshith257 is this fine #2339