fix: dependabot warnings

[lochie]

Package	Before	After	Dependabot #
rollup	2.79.2	2.80.0	#266
serialize-javascript	4.0.0	7.0.3	#273
minimatch	3.1.2	3.1.4	#264
underscore	1.12.1	1.13.8	#274
next	14.2.32	15.5.14	#242

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
connectkit-nextjs	Ready	Preview, Comment	Mar 27, 2026 2:21pm
connectkit-testbench	Ready	Preview, Comment	Mar 27, 2026 2:21pm
connectkit-vite	Ready	Preview, Comment	Mar 27, 2026 2:21pm

[github-actions]

Dependency Review

The following issues were found:

• ❌ 1 vulnerable package(s)

View full job summary

[Copilot]

Pull request overview

This PR aims to address Dependabot security warnings in the monorepo by updating tooling dependencies and enforcing patched transitive versions via Yarn resolutions/lockfile updates.

Changes:

• Bump rollup devDependency from ^2.79.2 to ^2.80.0.
• Add Yarn resolutions overrides for serialize-javascript@7.0.3 and minimatch@3.1.3.
• Update yarn.lock accordingly (including workspace entry and dependency graph changes).

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

File	Description
package.json	Updates build tooling version and adds resolutions pins intended to remediate vulnerable transitive deps.
yarn.lock	Regenerates/adjusts lock entries to reflect the new rollup version and enforced resolutions.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 3 changed files in this pull request and generated 2 comments.

Comments suppressed due to low confidence (1)

examples/testbench/package.json:20

• This workspace now uses next 15.5.14, but eslint-config-next is still pinned to 14.1.0 in devDependencies. Consider aligning them (or otherwise validating lint config compatibility) to avoid unexpected lint/ruleset mismatches.

    "next": "15.5.14",
    "react": "^18.0.0",
    "react-dom": "^18.0.0",
    "viem": "^2.23.2",
    "wagmi": "^2.14.11"

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 6 changed files in this pull request and generated 4 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This example updates to next@15.5.14, but keeps eslint-config-next on 12.3.0 (and thus @next/eslint-plugin-next@12.3.0). That combination is likely to produce incorrect or failing next lint behavior. Update eslint-config-next to a compatible v15 release for this workspace when bumping Next major versions.

[Copilot]

This workspace is now on next@15.5.14 but eslint-config-next remains on a v14 range. To keep next lint aligned with the installed Next major, update eslint-config-next to a v15 release in this workspace as well.

[Copilot]

This workspace is now on next@15.5.14 but eslint-config-next remains on a v14 range. To keep next lint aligned with the installed Next major, update eslint-config-next to a v15 release in this workspace as well.

Suggested change

	"eslint-config-next": "^14.0.4",
	"eslint-config-next": "^15.0.0",

[Copilot]

This example now depends on next@15.5.14 but keeps eslint-config-next@14.1.0. Consider bumping eslint-config-next to a v15 release here too so next lint uses rules/plugins that match the installed Next major version.