[SOLVED] zed official release v0.202.8 does not seem to exist.

dumbhardware · 2025-09-09 09:27:02

I use zed for to develop on a remote server. The latest version of zed on arch is v0.202.8. This tries to download a server of the same version in my remote which does not seem to exist at the moment - https://github.com/zed-industries/zed/releases. And hence it fails. I don't have an account in the arch linux gitlab repo so raising an issue here. I've worked around it by installing using the zed's official install script for now. Would be great if the version can be rolled back to v0.202.7 for now.

Last edited by dumbhardware (2025-09-11 08:06:28)

gromit · 2025-09-09 12:32:56

You can just get an account by sending an email:

Due to an influx of spam, we have had to temporarily disable account registrations. Please write an email to accountsupport@archlinux.org, with your desired username, if you want to get access. Sorry for the inconvenience.

Edit: Also it seems like the .8 tag exists, it's just not a proper release: https://github.com/zed-industries/zed/r … g/v0.202.8

Last edited by gromit (2025-09-09 12:35:29)

bulletmark · 2025-09-09 22:28:36

I wonder why you don't just continue to use the version installed by the zed install script? Zed updates itself automatically every time you run it and you can also switch easily to/from the preview version. The releases are so frequent (every few days or every day or two for preview) that the Arch package would usually be out of date. I usually stick to Arch packages but not for volatile user-only packages that self or easily update like zed.

Last edited by bulletmark (2025-09-09 23:40:48)

Succulent of your garden · 2025-09-09 23:43:19

bulletmark wrote:

I wonder why you don't just continue to use the version installed by the zed install script?

Because it's a script, not a binary, and you need to put a binary in the extra repos as far as I know, or someway to validate the authenticity of the package downloaded using a pgp key, which Arch Linux does to validate the updates integrity. So since you are talking in the extra repo, you need to validate that, because in Arch everything that is in the core and extra repos must be 100% that is fine, and not some kind of malware or intent to do, so the package maintainers need to check the supply chain very well so everyone can enjoy the packages in good conditions. So probably since the zed development team is very fast in doing PR in the repo, it seems that they are releasing very fast also, remember that Arch is a community effort distro also, which also seems to be the most up to date distro in Linux in my humble opinion

If you want to be up to date with zed editor maybe you can try the AUR version instead of the extra repo: https://aur.archlinux.org/packages/zed-git also check the PKGBUILD https://aur.archlinux.org/cgit/aur.git/ … ?h=zed-git

Be sure that you understand what the PKGBUILD is doing first, remember that the AUR is different than the core and extra repos, in the sense that Arch Linux doesn't guarantee that you can't add malware with the AUR, if you are using the AUR is your responsibility to make you system secure. But if you are only using core and extra then is the responsibility of the package mantainers, from a certain point of view.

Probably if you are going into the AUR version most probably you will need to compile Rust code using cargo, which probably is part of the PKGBUILD. The compiling in Rust could be slow in comparison to other languages if the project is big enough.

So long story Short:

If you keep in the extra repo package: Yeii signed and healthy package, but maybe not so up to date // probably just a couple of days to be honest, the mantainers are very fast in general.

If you go into the AUR: Yeii I always have the latest release in my machine, but it takes some time to compile it every day.

So pick your poison. Hope this post helps you.

EDIT:

If you really need to have package always up to date by some reason, and the AUR maintainer doesn't always has it, then you have two options:

Maybe create your own PKGBUILD.

Or add the zed repo to your list of repos in your system using the appropriate priority, but this last one I'm not sure if it is a good idea in this case. I know that is possible but you should also be sure to not fall into dependency hell in someway. If you manage to do that then you could always have the latest release in your computer, but to be honest be careful, I know it is possible but I'm not that experience enough to guide you properly, probably I would need a free day to learn some little things in more detail to be 100% that this is a good idea to you, since is an editor. But probably if you download only the binary release, then I don't see any point in not doing that, but only if you feel experience enough to do it so you don't break the system in some general update.

Last edited by Succulent of your garden (2025-09-09 23:56:02)

dumbhardware · 2025-09-11 08:05:05

Understood. It is not a massive pain point at the moment since I've found a work around. Will stick to the install script, while checking the official release versions before updating for now. Thanks folks!

Arch Linux

#1 2025-09-09 09:27:02

[SOLVED] zed official release v0.202.8 does not seem to exist.

#2 2025-09-09 12:32:56

Re: [SOLVED] zed official release v0.202.8 does not seem to exist.

#3 2025-09-09 22:28:36

Re: [SOLVED] zed official release v0.202.8 does not seem to exist.

#4 2025-09-09 23:43:19

Re: [SOLVED] zed official release v0.202.8 does not seem to exist.

#5 2025-09-11 08:05:05

Re: [SOLVED] zed official release v0.202.8 does not seem to exist.

Board footer