Almost daily updates are coming. Now it is 3.12.10, yesterday was 3.11.19, before that 3.11.10.
In the Changelog, you will see latest update at July 10th. What's New in Cursor — Latest Updates & Release Notes
Is there any other place to see what is changing at each release? Why changelog is not being updated?
The changelog is organized by feature (minor) release, not by patch build. Entries like 3.11 (Jul 10), 3.10, and 3.9 go out roughly weekly when a new feature version ships.
The near-daily bumps you’re seeing (3.11.10 → 3.11.19 → 3.12.10) are patch builds - bug fixes, stability, and staged rollouts that ship continuously. Those aren’t written up individually, so 3.11 being the latest entry is expected, the write-up for the next feature version follows when it goes out.
For another place to look, the in-app Release Notes link points to that same changelog, so it’s really the main spot today. There isn’t a separate per-patch changelog for the individual build numbers right now.
That said, I’d love for us to have more granular, per-patch notes too - I agree the gap between the rolling builds and the published changelog isn’t ideal, and it’s fair feedback to raise. We’re constantly rethinking on how we can do this better.
That’s the problem though: 3.12 is out but no release notes have been posted for it yet, site is still on 3.11, which is a first, we typically have release notes for every new feature version out at the same time as the binaries.
Just seconding this confusion - you show one patch version bump and one minor version bump in your example (3.11.10 → 3.11.19 → 3.12.10) and say that the 3.11 → 3.12 bump is not a feature release, but earlier in your message you describe the minor version numbers being associated with feature releases.
It seems like either:
Having a clearer explanation would be helpful!
+1 on this. We as a Workflow maintainer really want to know the detailed patch notes to determine if updating to the newest version will break our current Agentic workflow (we have had some issues in the past!) so we can decide on delaying the update to patch our workflow.