Between Command

between checks out two points in your git history, reads the lock files at each, and reports every package that differs. Where analyse looks at your working directory, between compares two committed states.

whatsdiff between <from> <to>

#Arguments

whatsdiff between abc123 def456

#Example output

composer.lock between v1.0.0 and v2.0.0

  ↑↑ laravel/framework    v11.0.0  →  v12.0.0  (15 releases)
  ↑↑ symfony/console      v6.4.0   →  v7.0.0   (8 releases)
   + laravel/sanctum      ^4.0
   + livewire/livewire    ^3.0
   × deprecated/package   ^1.0

#What it does

1. Checks out the <from> reference and reads the lock files
2. Checks out the <to> reference and reads the lock files
3. Compares the two states
4. Prints every package that changed between them

#When to use it

Code review. See what a branch did to your dependencies before you approve it, without reading a lock file diff.

Release notes. Work out which dependencies moved between two releases, and by how much.

Debugging. When something broke between two known-good points, the dependency list is often where the answer is.

#Related commands

• analyse compares your working directory instead of two commits
• check tests whether one specific package changed