dino diff meets your latest scan

`dino diff` now compares against your latest scan, macOS binaries are correctly code-signed, and new versions become available only once every download is ready.

dino diff now compares against your latest scan

Dino 1.1.5 fixes how dino diff tracks API changes.

Previously, dino diff and dino scan maintained separate snapshots. Now they share the same history, so dino diff compares your API against the latest state captured by dino scan.

The workflow is now straightforward:

1. Run dino scan to capture the current state of your API.
2. Make your changes.
3. Run dino diff to see exactly what changed.

If no previous scan exists, Dino automatically establishes a baseline for future comparisons.

In CI, run dino diff before dino scan. The Dino GitHub Action already follows this order.

More reliable macOS installs

Dino’s macOS binaries are now correctly code-signed, preventing macOS from incorrectly reporting browser-downloaded binaries as damaged.

If you download Dino directly through a browser, macOS may still ask you to approve it the first time you open it. Installs through Homebrew, npm, or the Dino installer require no additional steps.

Complete releases from day one

New Dino versions now become available only after all supported downloads are ready.

That means upgrading immediately after a release gives you the complete version regardless of how you install Dino.

Better guidance for coding agents

dino skill now points coding agents directly to the Dino GitHub Action and CI documentation, making it easier to set Dino up correctly in automated workflows.

dino docs --ai is now deprecated. The flag never changed the generated output, so it will continue working with a deprecation notice until a future major release.

Dino 1.1.5 also includes everything shipped in 1.1.4.