Arch Linux

saghmrossi

Member

Registered: 2026-03-24

Posts: 2

`cargo-tauri` not getting updated?

It looks like the `cargo-tauri` package is mistakenly not getting updated. From looking at the upstream repo, the latest version seems to be 2.10.1, and the package has been flagged as out of date for several months, but for some reason the work items on the package repo are getting closed by a bot claiming that 2.7.0 is the latest. Is anyone able to enlighten me on what's going on here? I tried to create an account to file a bug with the repo, but I apparently need to email to manually ask to be allowlisted for the project, so posting here is all I can do in the meantime.

gromit

Administrator

From: Germany

Registered: 2024-02-10

Posts: 1,519

Website

Re: `cargo-tauri` not getting updated?

This is due to the nvchecker file, you can download the repository and manually run `pkgctl version check` in it to see what it detects:
https://gitlab.archlinux.org/archlinux/ … type=heads

cg505

Member

Registered: 2025-12-15

Posts: 3

Re: `cargo-tauri` not getting updated?

At a quick glance, it seems likely due to a change in format of the git tags. I opened an MR https://gitlab.archlinux.org/archlinux/ … requests/2

saghmrossi

Member

Registered: 2026-03-24

Posts: 2

Re: `cargo-tauri` not getting updated?

Thanks for the explanation and for filing the the MR since I can't! I had used pkgctl in the past when I needed to manually update things when newer builds hadn't been published yet (e.g. when Discord updates made it impossible for me to join with older versions of the client), but I hadn't run into nvchecker before. It seems like maybe the longer term solution would be for nvchecker to have a way to validate that the latest tag matches a regex or something to avoid accidental detection like this, but at this point I'm pretty far outside of my past experience, so my confidence in how things should be handled is low. At the end of the day though, tags aren't really structured in any meaningful way, and upstreams are free to do whatever they want with their tags (even if it seems silly), so stuff like this might always fall through the cracks without human intervention.

It's nice to know that this ended up being caused by something relatively benign though; I admit I was slightly concerned at the idea of a bot making the judgment on whether something is a new version or not, so it's relieving to learning that it's a "traditional" bot rather than something more...experimental.