fix: solves #5336

[Pratham1812]

Proposed changes

Solves #5336

Types of changes

What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

• New feature (non-breaking change which adds functionality)
• Bugfix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices applies)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I have signed the commit for DCO to be passed.
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)

Dependency

• Please add the links to the dependent PR need to be merged before this (if any).

Special notes for your reviewer:

All the packages with critical vulnerabilities have been upgraded.

It was tested by running trivy fs . --severity HIGH,CRITICAL

[SarthakJain26]

Hi @Pratham1812, have you tried building the code after these changes? Please cross check if there are any breaking changes with the package upgrades

[PriteshKiri]

Hey @Pratham1812

Any updates on this?

[Pratham1812]

Hey @PriteshKiri and @SarthakJain26 have upgraded the dependencies and also fixed all the failing tests in the repo.

[Pratham1812]

Interestingly this vulnerability is not identified when I build the image locally (for graphql server) ->