update dependancy

[KnuffigerMaxi]

Description:

Feature: Updated project dependencies to their latest stable versions to improve security and compatibility. 

- Updated npm packages in package.json and yarn.lock
- Tested local builds to ensure no breaking changes

Labels:
devops / enhancement

Reviewers:
frontend / backend (or your team members)

How to Test:

1. Pull this branch
2. Run `yarn install` or `npm install`
3. Run the project locally (`npm start` or equivalent)
4. Verify the application starts and functions without errors

Related Issues:

Closes #<insert issue number if any>

Screenshots / Screen Recording:
Not applicable (no UI changes)

Checklist:

• Dev Review completed
• Dependencies updated without breaking the build
• Manually tested the changes

Notes for Reviewers:
Please check that all dependencies are compatible and the app builds without errors.

---

[welcome]

Welcome to the SigNoz community! Thank you for your first pull request and making this project better. 🤗

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
0 out of 2 committers have signed the CLA.

❌ snyk-bot
❌ KnuffigerMaxi
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 93c7916 in 1 minute and 12 seconds. Click for details.

• Reviewed 43 lines of code in 2 files
• Skipped 2 files when reviewing.
• Skipped posting 5 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. e2e/package.json:12

• Draft comment:
  Bumped dotenv from 8.2.0 to 8.6.0. Please verify that the updated version does not affect our test configuration or introduce any breaking changes.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

2. frontend/package.json:37

• Draft comment:
  Updated '@grafana/data' from ^11.2.3 to ^11.6.5. Confirm that all usages remain compatible with the new version.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

3. frontend/package.json:90

• Draft comment:
  Upgraded 'posthog-js' from 1.160.3 to 1.266.0. Ensure that the analytics integration continues to function without issues.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is about a dependency change, specifically the upgrade of 'posthog-js'. The comment asks the author to ensure that the analytics integration continues to function, which violates the rule against asking the author to ensure behavior is intended or tested. Therefore, this comment should be removed.

4. frontend/package.json:92

• Draft comment:
  Updated 'react' from 18.2.0 to 18.3.1. Please validate that component rendering and behavior remain unaffected by this update.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is about a dependency update, specifically the React library. The comment asks the PR author to validate that component rendering and behavior remain unaffected, which violates the rule against asking the author to ensure behavior is intended or tested. Additionally, it involves a library version change, which is not recognized as a valid comment topic according to the rules.

5. frontend/package.json:97

• Draft comment:
  Updated 'react-dom' from 18.2.0 to 18.3.1. Confirm that DOM rendering and hydration work as expected after this upgrade.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is about a dependency change, specifically the version update of 'react-dom'. The comment asks the PR author to confirm that DOM rendering and hydration work as expected after the upgrade. This falls under the rule of not asking the PR author to confirm or ensure behavior, especially for dependency changes.

Workflow ID: wflow_DwMNqzHQOEOYXURK

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}