chore: upgrade to ENSv2 (Universal Resolver)

[Dhaiwat10]

Hey! I'm Dhaiwat from the DevRel team at ENS Labs. We're working on getting active repos and libraries across the ecosystem ready for ENSv2.

Summary

Upgrades this repo to be ENSv2-ready by routing ENS resolution through the Universal Resolver (0xeeeeeeee14d718c2b47d9923deab1335e144eeee) instead of the legacy ENS Registry.

Changes

• Upgrade viem ^2.30.2 → ^2.48.11 in apps/contracts/package.json
• Upgrade viem ^2.30.2 → ^2.48.11 in apps/dapp/package.json
• Upgrade viem ^2.30.2 → ^2.48.11 in packages/constants/package.json
• Upgrade viem ^2.30.2 → ^2.48.11 in packages/forms/package.json
• Upgrade viem ^2.30.2 → ^2.48.11 in packages/graphql/package.json
• Upgrade viem ^2.30.2 → ^2.48.11 in packages/hooks/package.json
• Upgrade viem ^2.30.2 → ^2.48.11 in packages/types/package.json
• Upgrade viem ^2.30.2 → ^2.48.11 in packages/ui/package.json
• Upgrade viem ^2.30.2 → ^2.48.11 in packages/utils/package.json

Why

The current path returns stale results for names managed by the new Universal Resolver. For example, ur.integration-tests.eth should resolve to 0x2222222222222222222222222222222222222222; legacy resolution returns incorrect values.

More details: https://docs.ens.domains/web/ensv2-readiness

Verification

• ur.integration-tests.eth → 0x2222222222222222222222222222222222222222

Summary by CodeRabbit

• Chores
  • Updated a core blockchain library dependency to the latest compatible version across all applications and packages for improved compatibility and feature access.

[vercel]

Someone is attempting to deploy a commit to the Smart Invoice Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9abca468-7402-48dc-b223-62dac3649726

📥 Commits

Reviewing files that changed from the base of the PR and between 01a012c and 5033cda.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (9)

• apps/contracts/package.json
• apps/dapp/package.json
• packages/constants/package.json
• packages/forms/package.json
• packages/graphql/package.json
• packages/hooks/package.json
• packages/types/package.json
• packages/ui/package.json
• packages/utils/package.json

---

📝 Walkthrough

Walkthrough

This PR updates the viem dependency from ^2.30.2 to ^2.48.11 uniformly across nine package.json files in the monorepo, spanning both application and package layers to ensure consistent dependency versioning.

Changes

viem Dependency Upgrade

Layer / File(s)	Summary
Dependency Version Updates apps/contracts/package.json, apps/dapp/package.json, packages/constants/package.json, packages/forms/package.json, packages/graphql/package.json, packages/hooks/package.json, packages/types/package.json, packages/ui/package.json, packages/utils/package.json	The viem dependency is upgraded from ^2.30.2 to ^2.48.11 across all package.json files in the monorepo.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A viem so new, from thirty to forty-eight hops,
Across the packages, this upgrade never stops,
Consistent versions dance in JSON delight,
The monorepo shines with dependency might! 🌟

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title clearly and specifically describes the main change: upgrading viem across multiple packages to support ENSv2 via the Universal Resolver.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}