Skip to content

Conversation

@yashhhguptaaa
Copy link

@yashhhguptaaa yashhhguptaaa commented Dec 28, 2025

Issue: #614


Summary

Upgrade Relay from v19.0.0 to v20.1.1 across all applications and packages. This update enables future schema splitting capabilities and ensures all Relay-related packages are aligned to the same version.

Changes

Dependencies Updated

Console App (apps/console/package.json):

  • react-relay: ^19.0.0 → ^20.1.1
  • relay-runtime: ^19.0.0 → ^20.1.1
  • relay-compiler: ^19.0.0 → ^20.1.1 (dev)
  • babel-plugin-relay: ^19.0.0 → ^20.1.1 (dev)

Trust App (apps/trust/package.json):

  • react-relay: ^19.0.0 → ^20.1.1
  • relay-runtime: ^19.0.0 → ^20.1.1
  • relay-compiler: ^19.0.0 → ^20.1.1 (dev)
  • babel-plugin-relay: ^19.0.0 → ^20.1.1 (dev)

Routes Package (packages/routes/package.json):

  • Updated peerDependencies to require react-relay and relay-runtime ^20.1.1

Type Definitions:

  • Kept @types/react-relay (^18.2.1) and @types/relay-runtime (^19.0.1) as Relay v20 does not include built-in TypeScript definitions

Verification

  • ✅ Relay compiler runs successfully for both console and trust apps
  • ✅ TypeScript compilation passes without errors
  • ✅ Build completes successfully for both applications
  • ✅ No breaking changes detected in existing Relay code (uses modern useMutation API)

Migration Steps

  1. Install dependencies:
    npm install
  2. Regenerate Relay artifacts:
    npm run relay
  3. Verify builds:
    npm run build

Benefits

  • Enables GraphQL schema splitting into multiple files (as mentioned in Update relay to latest #614)
  • Aligns all Relay packages to the same version, preventing version mismatches
  • Keeps the codebase up-to-date with the latest Relay improvements and bug fixes

@yashhhguptaaa yashhhguptaaa marked this pull request as ready for review January 1, 2026 19:16
Copy link

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 4 files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant