Should comparison tables show a checked date for every row?

Discusses date visibility for volatile comparison rows such as pricing, limits, and eligibility.

Comparison tables look more reliable than they are when every row has the same visual weight. A row checked this week and a row checked six months ago can sit next to each other with no warning. For prices, API limits, eligibility rules, supported regions, or deadlines, I think a checked-date column is part of the answer. Do you prefer row-level dates, field-level notes, or a single page-level review date?