chore: upgrade packages to latest versions #1072
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Date:
change date hereDeveloper Name:
developer name hereIssue Ticket Number:-
#923Description:
Add description of the PR here
Is Under Feature Flag
Database changes
Breaking changes (If your feature is breaking/missing something please mention pending tickets)
Is Development Tested?
Tested in staging?
Add relevant Screenshot below ( e.g test coverage etc. )
Description by Korbit AI
What change is being made?
Upgrade all packages to their latest versions, update Node.js version in CI workflows to 22.x, refactor template files for improved code readability, and create a new ESLint configuration.
Why are these changes being made?
The upgrades ensure that the codebase benefits from the latest features, security patches, and performance improvements. Transitioning Node.js version aligns with the end of life of previous versions. Code refactoring in templates reduces verbosity, making it easier to maintain and understand, while the new ESLint configuration provides better developer tooling support and conformity with modern coding standards.