# Upgrade and release notes

**URL:** <https://forum.cursor.com/t/upgrade-and-release-notes/40016>\
**Category:** Feedback\
**Created:** [January 8, 2025, 4:38pm UTC](https://forum.cursor.com/t/upgrade-and-release-notes/40016 "2025-01-08T16:38:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![robertoranon](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/robertoranon/32/19080_2.png) [@robertoranon](https://forum.cursor.com/u/robertoranon)\
**Post date:** [January 8, 2025, 4:38pm UTC](https://forum.cursor.com/t/upgrade-and-release-notes/40016/1 "2025-01-08T16:38:45Z")

</div>

Hi,

a few hours ago, Cursor asked me to upgrade. When I followed the link to the changes, the page still reports version 44 (dec 17).  
Guys, this is not acceptable for a product that costs 240$ per year.  
You need to:

- be clear whether upgrades are mandatory or not (will it update anyway sooner or later, as it happened in the past? if I need to stay with the current version for consistency, how long will I be able to do so? can I downgrade?). Btw these info need to be in a web page, not in some random answer to someone in the forum.
- publish release notes in synch with the upgrade request
- btw, release notes could be a bit more worldly? they are quite cryptic so far

However useful and nice Cursor is, for me it’s a work tool and first and foremost it has to be reliable. I am not renewing my monthly subscription if these issues are not addressed.

---

<div class="post-metadata">

**Author:** ![robertoranon](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/robertoranon/32/19080_2.png) [@robertoranon](https://forum.cursor.com/u/robertoranon)\
**Post date:** [January 8, 2025, 5:06pm UTC](https://forum.cursor.com/t/upgrade-and-release-notes/40016/2 "2025-01-08T17:06:45Z")

</div>

I’ve found a post in the forum where you explain why release notes are not published until the update cycle is complete, but I cannot believe you would like that for your software of choice.  
You can link to a a page in the forum with pre-release notes, and you can label the update as beta, if it is so.  
But I cannot trust an upgrade without release notes and knowing wether I can downgrade. Not for a work tool.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [June 18, 2026, 10:23am UTC](https://forum.cursor.com/t/upgrade-and-release-notes/40016/3 "2026-06-18T10:23:55Z")

</div>

Closed on June 18, 2026, 10:23am UTC


