How do small dev teams use simple update logs to build trust with buyers?

When evaluating new tools, I’ve started ignoring flashy marketing pages and heading straight for the product's changelog.

Seeing steady weekly fixes and listening to real feedback tells me way more about the team's momentum than a row of testimonials.

Framing every update around a user headache like "fixed slowdowns on big exports" instead of vague tech speak—makes a massive difference in showing care.

Has publishing a public release history helped your conversion rates, or do you find most visitors ignore it?