chore(deps): batch dependabot updates (9 safe + 1 type-compat fix) - #175
Merged
Conversation
Bumps [dotenv](https://github.com/motdotla/dotenv) from 17.4.1 to 17.4.2. - [Changelog](https://github.com/motdotla/dotenv/blob/master/CHANGELOG.md) - [Commits](motdotla/dotenv@v17.4.1...v17.4.2) --- updated-dependencies: - dependency-name: dotenv dependency-version: 17.4.2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [@modelcontextprotocol/ext-apps](https://github.com/modelcontextprotocol/ext-apps) from 1.5.0 to 1.7.1. - [Release notes](https://github.com/modelcontextprotocol/ext-apps/releases) - [Changelog](https://github.com/modelcontextprotocol/ext-apps/blob/main/RELEASES.md) - [Commits](modelcontextprotocol/ext-apps@v1.5.0...v1.7.1) --- updated-dependencies: - dependency-name: "@modelcontextprotocol/ext-apps" dependency-version: 1.6.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [react-dom](https://github.com/facebook/react/tree/HEAD/packages/react-dom) from 19.2.4 to 19.2.5. - [Release notes](https://github.com/facebook/react/releases) - [Changelog](https://github.com/facebook/react/blob/main/CHANGELOG.md) - [Commits](https://github.com/facebook/react/commits/v19.2.5/packages/react-dom) --- updated-dependencies: - dependency-name: react-dom dependency-version: 19.2.5 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [react](https://github.com/facebook/react/tree/HEAD/packages/react) from 19.2.4 to 19.2.5. - [Release notes](https://github.com/facebook/react/releases) - [Changelog](https://github.com/facebook/react/blob/main/CHANGELOG.md) - [Commits](https://github.com/facebook/react/commits/v19.2.5/packages/react) --- updated-dependencies: - dependency-name: react dependency-version: 19.2.5 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [@supabase/supabase-js](https://github.com/supabase/supabase-js/tree/HEAD/packages/core/supabase-js) from 2.102.1 to 2.105.1. - [Release notes](https://github.com/supabase/supabase-js/releases) - [Changelog](https://github.com/supabase/supabase-js/blob/develop/packages/core/supabase-js/CHANGELOG.md) - [Commits](https://github.com/supabase/supabase-js/commits/v2.105.1/packages/core/supabase-js) --- updated-dependencies: - dependency-name: "@supabase/supabase-js" dependency-version: 2.103.3 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [inquirer](https://github.com/SBoudrias/Inquirer.js) from 13.4.0 to 13.4.2. - [Release notes](https://github.com/SBoudrias/Inquirer.js/releases) - [Commits](https://github.com/SBoudrias/Inquirer.js/compare/inquirer@13.4.0...inquirer@13.4.2) --- updated-dependencies: - dependency-name: inquirer dependency-version: 13.4.2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [next](https://github.com/vercel/next.js) from 16.2.2 to 16.2.4. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v16.2.2...v16.2.4) --- updated-dependencies: - dependency-name: next dependency-version: 16.2.4 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [actions/create-github-app-token](https://github.com/actions/create-github-app-token) from 2 to 3. - [Release notes](https://github.com/actions/create-github-app-token/releases) - [Commits](actions/create-github-app-token@v2...v3) --- updated-dependencies: - dependency-name: actions/create-github-app-token dependency-version: '3' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [pnpm/action-setup](https://github.com/pnpm/action-setup) from 4 to 6. - [Release notes](https://github.com/pnpm/action-setup/releases) - [Commits](pnpm/action-setup@v4...v6) --- updated-dependencies: - dependency-name: pnpm/action-setup dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
…pm/action-setup-6' into chore/dependabot-batch
…tions/create-github-app-token-3' into chore/dependabot-batch
…base/supabase-js-2.103.3' into chore/dependabot-batch
…-16.2.4' into chore/dependabot-batch
…irer-13.4.2' into chore/dependabot-batch
…lcontextprotocol/ext-apps-1.6.0' into chore/dependabot-batch
…t-19.2.5' into chore/dependabot-batch
…nv-17.4.2' into chore/dependabot-batch
…t-dom-19.2.5' into chore/dependabot-batch
Co-authored-by: Cursor <cursoragent@cursor.com>
…y-pick #169) Co-authored-by: Cursor <cursoragent@cursor.com>
The sequential merges with -X theirs strategy left a few package.json entries holding their pre-bump version when a later merge's branch file overwrote an earlier merge's entry. Restore the intended state: - react ^19.2.4 → ^19.2.5 across 7 example apps + packages/react (PR #94 was overwritten by the later PR #91 react-dom merge) - next ^16.2.1 → ^16.2.4 in examples/checkout-demo, hosted-checkout-demo, shadcn-checkout (PR #111 was overwritten by later merges) - examples/shared next bumped via 'pnpm update next' to dedupe the 16.2.2/16.2.4 split that was leaving examples/tailwind-checkout failing typecheck against two next versions - pnpm-lock.yaml regenerated by 'pnpm install' Co-authored-by: Cursor <cursoragent@cursor.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 616bbea. Configure here.
| - name: Generate release-bot token | ||
| id: app-token | ||
| uses: actions/create-github-app-token@v2 | ||
| uses: actions/create-github-app-token@v3 |
There was a problem hiding this comment.
Deprecated app-id input used with create-github-app-token@v3
Low Severity
The bump from actions/create-github-app-token@v2 to @v3 means the workflow now resolves to v3.1.0+, which deprecated the app-id input in favor of client-id. While app-id still works as a fallback today, it may be removed in a future v3.x release, potentially breaking the publish workflow without warning.
Reviewed by Cursor Bugbot for commit 616bbea. Configure here.
This was referenced May 5, 2026
dhruv-sanan
pushed a commit
to dhruv-sanan/solvapay-sdk
that referenced
this pull request
May 8, 2026
…pat fix After syncing main → dev, the dependabot batch (PR solvapay#175) leaves the following published-package changes that need changesets to ship: - @solvapay/react: McpApp.tsx event-listener type relaxation (real source fix for ext-apps@^1.7 compat) - @solvapay/mcp: peerDep range bump for @modelcontextprotocol/ext-apps ^1.5.0 → ^1.7.1 (consumer-visible) - solvapay (CLI): runtime inquirer ^13.3.2 → ^13.4.2 - @solvapay/server: runtime dotenv ^17.4.1 → ^17.4.2 - @solvapay/next: devDep next ^16.2.1 → ^16.2.4 (empty changeset — no consumer-visible change) Resulting plan (pnpm exec changeset status --verbose): solvapay 1.0.8 → 1.0.9 @solvapay/mcp 0.2.4 → 0.2.5 @solvapay/react 1.1.3 → 1.1.4 @solvapay/server 1.0.11 → 1.0.12 @solvapay/next 1.0.10 → 1.0.11 (cascade from @solvapay/server) All patch bumps. No major cascade because every consumer dependency range stays in-range across patch boundaries. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Summary
Bundles 9 safe dependabot PRs into one merge so we trim the open-PR queue and avoid 9 separate CI roundtrips. Also folds in PR #169 (a 4-line type-compat fix that's needed when ext-apps@1.7+ is bumped — without it the example builds fail typecheck).
What's bundled
CI workflow bumps
Runtime/dev dep bumps
Type-compat fix bundled in
packages/react/src/mcp/McpApp.tsx: relaxaddEventListener/removeEventListenerevent arg fromstringtoany. ext-apps@1.7+ tightened the event type toK extends keyof AppEventMap, breaking the loose shapeMcpAppFulldeclared. 4-line fix, cherry-picked from PR fix(react): relax event listener type to maintain compatibility with ext-apps #169 (which was opened against this exact incompatibility but never merged). Closes fix(react): relax event listener type to maintain compatibility with ext-apps #169.Skipped (need separate handling)
Methodology + caveat
Sequential
git merge -X theirsfor the 9 dependabot branches, thenpnpm installto reconcile the lockfile. The-X theirsstrategy auto-resolves conflicts in the incoming branch's favour, but for files touched by multiple bumps (e.g.examples/checkout-demo/package.jsonis touched by 4 PRs) the LATEST merge's whole file wins — silently reverting earlier bumps in the same file. I caught this when the build broke ontailwind-checkouttypechecking against two next versions, audited every multi-bump file (8 affected), and patched the missed bumps in commit616bbea(`react ^19.2.4 → ^19.2.5` in 7 files, `next ^16.2.1 → ^16.2.4` in 3 files). Also bumpedexamples/sharednext via `pnpm update` to dedupe the 16.2.2/16.2.4 split.Test plan
Made with Cursor
Note
Low Risk
Low risk dependency and GitHub Actions version bumps; the only code change relaxes
McpAppevent listener typing to restore compatibility with@modelcontextprotocol/ext-apps@1.7+.Overview
Dependency/CI maintenance batch. Updates GitHub Actions used in workflows (
pnpm/action-setup@v6,actions/create-github-app-token@v3) and bumps multiple JS deps across packages/examples (notablynext,react/react-dom,@supabase/supabase-js,dotenv,inquirer, and@modelcontextprotocol/ext-apps), with correspondingpnpm-lock.yamlrefresh.Type compatibility fix. Adjusts
packages/reactMcpAppFullto accept non-string event keys by looseningaddEventListener/removeEventListenerevttyping, keeping builds type-safe after theext-appsupgrade.Reviewed by Cursor Bugbot for commit 616bbea. Bugbot is set up for automated code reviews on this repo. Configure here.