dino diff

​

Usage

dino diff --tenant <id> [flags]

​

Flags

​

How It Works

1. Discover — Introspects the live API schema
2. Build snapshot — Creates a snapshot of the current schema
3. Load previous — Reads the most recent snapshot from disk
4. Diff — Compares previous vs. current and categorizes changes
5. Save — Writes the current snapshot as the new baseline

First snapshot saved.

​

Examples

​

Check for schema changes

dino diff --tenant acme --env staging

# Schema Diff — acme / staging

## Summary
  Added: 3 | Removed: 1 | Modified: 2 | Breaking: 1

## Breaking Changes
  - Removed field `User.legacyId`

## Added
  - Field `User.avatarUrl`
  - Field `User.preferences`
  - Query `searchUsers`

## Modified
  - Field `User.email` — type changed (String → String!)

​

CI gate for breaking changes

dino diff --tenant acme --env production --fail-on-breaking

- name: Schema compatibility check
  run: dino diff --tenant acme --env production --fail-on-breaking

schema-check:
  script:
    - dino diff --tenant acme --env production --fail-on-breaking

​

JSON output for tooling

dino diff --tenant acme --format json > diff.json

​

Exit Codes

​

Related

• dino scan — Full pipeline run (also saves snapshots)
• dino changelog — Changelog from the same diff data
• dino lint — Audit SDL description coverage