Renovate updates

[amitsingh-007]

Check if the Pull Request fulfils these requirements

• Does manifest.base.json requires version change?

---

Greptile Overview

Greptile Summary

This PR updates various dependencies via Renovate and upgrades GitHub Actions versions. The changes include:

• Updated GitHub Actions: checkout@v6, cache@v5, upload-artifact@v6, download-artifact@v7
• Dependency updates: Mantine (8.3.6 → 8.3.14), TRPC (11.7.1 → 11.9.0), React (19.2.0 → 19.2.4), Next.js (16.0.7 → 16.1.6), and many others
• Code formatting: Import statement reformatting in AuthProvider.tsx (prettier)

Critical Issue:
The artifact action versions are incompatible. upload-artifact@v6 and download-artifact@v7 cannot be used in the same workflow run - artifacts uploaded with v6 cannot be downloaded with v7. This affects both playwright.yml and release.yml workflows and will cause workflow failures.

Required Fix:
Either downgrade download-artifact to v6 or upgrade upload-artifact to v7 to ensure compatibility.

Confidence Score: 1/5

• This PR has critical workflow failures that will prevent CI/CD pipelines from running successfully
• The artifact version incompatibility between upload-artifact@v6 and download-artifact@v7 will cause immediate workflow failures in both playwright.yml and release.yml. While dependency updates are generally safe, the broken CI/CD pipelines make this PR unsafe to merge in its current state
• .github/workflows/playwright.yml and .github/workflows/release.yml require immediate attention to fix artifact action version mismatches

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 4 additional flags.

[gemini-code-assist]

Code Review

This pull request updates several dependencies across the monorepo. Most of these are minor or patch updates and should be safe to merge. A notable change is the major version update for the vercel CLI from v48 to v50. It's important to be aware that major version changes can introduce breaking changes that might affect deployment workflows. I've also added a few suggestions to improve dependency management by deduplicating some development dependencies. Hoisting them to the root package.json will simplify maintenance and ensure version consistency across all workspaces.

[greptile-apps]

_{2 files reviewed, 4 comments}

_{Edit Code Review Agent Settings | Greptile}

[coderabbitai]

Warning

Rate limit exceeded

@amitsingh-007 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 19 minutes and 20 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📝 Walkthrough

Walkthrough

Workflow files (.github/workflows/*.yml) were updated to newer action versions (checkout v5→v6, upload-artifact v5→v6, cache v4→v5, download-artifact v6→v7) with no control-flow changes. Multiple package.json files across the monorepo had dependency and devDependency version bumps (root, apps/extension, apps/web, packages/shared, packages/trpc). packageManager updated to pnpm@10.28.2. apps/web/next-env.d.ts import path was changed, and a dynamic import in apps/web/src/app/provider/AuthProvider.tsx was reformatted.

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check	❓ Inconclusive	The title 'Renovate updates' is vague and generic, using non-descriptive language that doesn't convey meaningful information about the changeset.	Consider a more specific title that highlights the main concern, such as 'Update dependencies via Renovate' or 'Upgrade GitHub Actions and dependencies' to better reflect the actual changes.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description fulfills the repository template by checking the manifest.base.json requirement and provides comprehensive context about the updates and critical compatibility issues.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch renovate-updates

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.github/workflows/playwright.yml:
- Line 14: The workflow upgrades several GH Actions to new major versions
(actions/checkout@v6, actions/upload-artifact@v6, actions/download-artifact@v7,
actions/cache@v5, actions/setup-node@v6) that introduce runner-version and
behavioral breaking changes; either revert those steps to their
last-known-compatible tags (e.g., checkout v5, upload/download-artifact v5/v6,
cache v4) or add explicit documentation and checks that self-hosted runners meet
the minimum runner versions (>=2.327.1/2.329.0 as noted) and confirm setup-node
v6’s changed automatic caching is intentionally compatible with the explicit
actions/cache usage—update the workflow comments/README and any on-prem runner
upgrade docs accordingly so maintainers know the required runner versions and
caching implications.

[webext-bot]

Extension Size Change:   1.06 KB 🔺

Commit	6b16157
Latest release size	174.24 KB
Current size	175.30 KB
Percent change	0.61 %

---

This commit looks good, cheers 👏

[webext-bot]

Extension version is updated from 22.33.0 to 22.34.0

[webext-bot]

Extension Size Change:   1.06 KB 🔺

Commit	3d3122a
Latest release size	174.24 KB
Current size	175.29 KB
Percent change	0.61 %

---

This commit looks good, cheers 👏

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional flag.