RPM release via repositories are not up-to-date

Bug Reports
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

RPM releases published to the repository (to allow for yum/dnf upgrades) are not published when the main builds are published.

Right now I can download 2.0 from the website “cursor-2.0.34.el8.x86_64.rpm”

However when I do a “sudo dnf upgrade cursor --refresh” there are no updates.

I previously reported this here on this thread: RPM on Fedora 42 does not upgrade with package manager - #7 by tecnobrat as a comment.

This has been a consistent problem. Cursor will report a new version in cursor itself, I’ll run a dnf upgrade and it won’t find any new versions.

Can we ensure that ALL versions are pushed at the same time so that we don’t get mismatched messages about available upgrades?

Steps to Reproduce

Try to upgrade to cursor 2.0 right now using yum/dnf

Expected Behavior

The 2.0 upgrade should be available.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.54
VSCode Version: 1.99.3
Commit: 5c17eb2968a37f66bc6662f48d6356a100b67be0
Date: 2025-10-21T19:07:38.476Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Linux x64 6.16.12-200.fc42.x86_64

Does this stop you from using Cursor

No - Cursor works, but with this issue

2 Likes
2

I can also confirm that the manifest file is definitely not updated – or its cached at the edge: https://downloads.cursor.com/yumrepo/repodata/repomd.xml

<timestamp>1761122004</timestamp>

<timestamp>1761121997</timestamp>

irb(main):001> Time.at(1761121997)
=> 2025-10-22 01:33:17 -0700
irb(main):003> Time.at(1761122004)
=> 2025-10-22 01:33:24 -0700
1 Like
3

Hey, thanks for the report - I believe this should have been updated now!

1 Like
4

@danperks can you explain why the versions don’t match everywhere?

If I go to the website, right now, I can download only cursor-2.0.34.el8.x86_64.rpm

I ran a dnf upgrade and I got “cursor-0:2.0.43-1761851158.el8.x86_64”

Why are the versions different? Why does it seem like the RPM on the repo are always different or delayed?

1 Like
5

We have a custom updating system which allows us to do things like phased rollouts of releases, and also allows us to handle release streams (Release, Pre-release, Nightly).

Package managers do not conform to this system, and instead get updated daily with the latest publicly available version. This can mean that the two sources may occasionally not be in sync, especially on or following a major update, where there may be a higher-than-normal frequency of updates and patches.

6

@danperks, Snap conforms to this. However, ignoring Flatpak’s half-baked branch system, all other package managers (Microsoft’s WinGet, Fedora’s DNF5, openSUSE’s Zypper, and Debian’s apt, alongside their correspondent official repositories) expect packages with the same base name, but different suffixes:

cursor-release
cursor-pre-release
cursor-nightly

Considering that Chrome manages to provide these, I doubt that you can’t.