Follow changes over time

How candidates chain during a testing session and how release history compares accepted versions.

In short

Each time an endpoint's answer differs from what was last seen, a new version is made and compared with the one right before it. Ten runs of a changing endpoint give a readable chain instead of ten copies of the same difference. Release history compares only the versions you accepted.

Before you start

Who: anyone who can open the project (View).
Plan: change intelligence must be on your plan.
First: at least two versions of an endpoint's contract.

Steps

Open a change report and scroll to "Release history".
Select a version to compare it with the one accepted before it.

Result: you see what changed since you last shipped, without the candidates in between.

Good to know

An identical repeat run creates nothing.
You need not review each candidate. Several can stay Pending while you work.
Accepting any candidate sets every older unreviewed one for that endpoint to Superseded. They are not deleted.

If something goes wrong

The first accepted version cannot be selected: it has nothing earlier to compare with.