Currently the steam package's `PKGBUILD` gets its "source code"[1] from <https://repo.steampowered.com/steam/pool/>, but that directory is an apt package pool (the apt/dpkg/.deb equivalent of ftp.archlinux.org). Like Arch packages, it's normal for each version to disappear from that location when it gets superseded, making it impossible to rebuild Arch's package from "source" after that happens. `.nvchecker.toml` watches for new versions in the same apt package pool. Please switch to monitoring and downloading from either: * <https://repo.steampowered.com/steam/archive/beta/>, if you want to see Valve's new releases as soon as they're published as a beta (this is the equivalent of what's currently done, because the package pool contains the current stable and the current beta at any given time) * or <https://repo.steampowered.com/steam/archive/stable/>, if you want to wait until each release is considered stable (I thought Arch's policy was usually to do this) That way, it will always be possible to rebuild Arch's package from its PKGBUILD, even if it's currently out of date. New beta releases appear in `steam/pool/` and `steam/archive/beta/` at the same time, and in the apt metadata they're listed in `steam/dists/beta/`. If a release has been tested a bit and is marked as stable (this doesn't always happen, for example 1.0.0.80 was never a stable release), it gets copied into `steam/archive/stable/` and added to the metadata in `steam/dists/stable/`. --- [1] actually mostly proprietary binaries, but it behaves like source code for the purposes of how it gets packaged