Show what is the update

Describe the Bug

Cursor suggest to install new version, but it is unclear, what the new version is.

Steps to Reproduce

  1. NA

Expected Behavior

I expect to see info what is the new version. And button clicking should open dialog with more detailed information.

Operating System

MacOS

Version Information

NA. dfdfdfdfdff

Does this stop you from using Cursor

No - Cursor works, but with this issue

3 Likes


Posting picture here, because the first dialog does not allow CTRL+V.

1 Like

I usually edit my original post after submitting it to add images.

The update is almost always for the latest version. I agree it would be nice if they told us the version, but would it even help if they tell us the version? It’s not like there are any changelogs to know what you are getting yourself into. I find that it is better to just disable all auto updates and update manually via Help menu or by reinstalling.

1 Like

Hey, thanks for the report. This is a common request, and the team is aware of it.

For now, you can check what’s included in an update on the Changelog page: Changelog · Cursor

Updates are rolled out in stages, so sometimes the notification shows up before the changelog is published on the site.

1 Like

Is there a more granular changelog. The link provided shows only changes for 2.6. Is there a way to see changes for a specific version, like 2.6.19?

Hey, yeah, you’re right. Right now the changelog only shows major and minor versions, and patch versions aren’t shown there at the moment.

Thanks, I’ll pass this on to the team.

So if I am on Cursor Nightly it will actually downgrade my version, right? You link point to the previous changelog ((

If you’re on Cursor Nightly, the update notification should offer a newer Nightly build. It shouldn’t downgrade you to Stable. Nightly and Stable update through different channels.

If you’re not sure, you can check your current version in Help > About and compare it with the version shown in the update prompt. If you notice that your version got lower after updating, let me know, that’s definitely a bug.

About showing the version in the notification and having a more detailed changelog, I’ve passed both requests to the team and they’re on the radar.

1 Like

I clicked “Restart to Update” and it seems stuck. It is already 10mins pass and nothing happened…

When I clicked “Force Quit” for some reason “Docker Desctop” crashed:

After running DockerDesktop and Cursor again I see that Cursor have correct newer Nightly version :+1:

though it still have this problem with missed file:
```
❯ ge 1
cursor-nightly ../../../env-level/pd/.terraform.lock.hcl
Error reading NLS messages file /Applications/Cursor Nightly.app/Contents/Resources/app/out/nls.messages.json: Error: ENOENT: no such file or directory, open ‘/Applications/Cursor Nightly.app/Contents/Resources/app/out/nls.messages.json’

on  feature/PC-18744_Centralize_pipelines [$!?] via :snake: v3.14.3 (.venv) via :diamond_with_a_dot: default
❯ cursor-nightly --version
Error reading NLS messages file /Applications/Cursor Nightly.app/Contents/Resources/app/out/nls.messages.json: Error: ENOENT: no such file or directory, open ‘/Applications/Cursor Nightly.app/Contents/Resources/app/out/nls.messages.json’
2.7.0-pre.76.patch.0
dbf1f1e2fb595868a79f3c011f76fc41eeb20b29
arm64
```

Glad the update eventually went through and you’re on the correct version.

About the Restart to Update hang, that’s a known issue with Nightly updates. The team is aware. If it happens again, Force Quit plus a manual relaunch is a solid workaround, like you did.

Docker Desktop crashing after Force Quit is probably a coincidence. macOS sometimes terminates related processes when you force-close an app. If it keeps happening specifically when closing Cursor, let me know.

For the nls.messages.json error, I see we’re already discussing it in your other thread Error when I use -w option. The file is still missing in the new version too. I’ll share this with the team along with both examples. Let’s keep tracking it there.

1 Like

@deanrie please note the first 2 comments are about the ongoing issue that we can’t paste images to bug reports, like we can with every other forum post.

Please can someone address this?

2 Likes

Bug reports are using a form to format your post which does not allow pasted images. Ideally the text areas in the form could receive pasted images, but I think they are unformatted text areas as of now. The workaround is to immediately edit the post after submitting the bug report, which then behaves like a normal post and can add the images like normal then.

Yep, that’s exactly the issue.

No reason whatsoever for disabling pasting images, and I wonder how many bug reports are given up mid composing - I’ve certainly dropped about 75% submissions are the effort required is too high.

Might be a deliberate filter though!

The problem is if I keep image in my buffer then I can not copy/paste the cursor version. If I do, then I will lost my screenshot with a bug.

Fair point. If you are using Windows, pressing “Windows Key + V” allows you to have clipboard history which you can then paste a screenshot from before. The overall bug form is hassle. I use Greenshot to take screenshots which has the option to save it or open it up in an image editor, which can help preserve the screenshot.