feat: enable latest sepolia namespace with ensv2

[shrugs]

updates the sepolia datasource to include the ensv2 contracts

[changeset-bot]

⚠️ No Changeset found

Latest commit: 42a3165

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
admin.ensnode.io	Ready	Preview, Comment	Jan 13, 2026 2:08am
ensnode.io	Ready	Preview, Comment	Jan 13, 2026 2:08am
ensrainbow.io	Ready	Preview, Comment	Jan 13, 2026 2:08am

[lightwalker-eth]

@shrugs Thanks for updates. Seeking your advice, thanks 👍

[lightwalker-eth]

Can you help me understand how to think about the updates here?

I'm wondering if we should represent these changes as a sepolia-v2 namespace such that we make no changes to the existing sepolia namespace?

Has the broader ENS ecosystem transitioned to these new Sepolia contracts, or is it only the new apps being built by the ENS Labs team?

Is the official ENS manager app on Sepolia transitioned to these new Sepolia contracts?

Appreciate your advice, thanks 👍