This a fascinating and weird bug, looks good to me.
Next time try to avoid opening, closing and then reopening the same PR, and create an issue discussing the bug before opening a PR, so you won't work needlessly for something that might get closed.

Hello.

Are you sure this is a proper fix? I get this right now

bob --version
bob-nvim 4.1.5

bob list-remote
2025-11-24T16:24:09.529972Z ERROR Error: Cannot find stable release

curl -i "https://api.github.com/repos/neovim/neovim/releases?per_page=15" | grep -o '"tag_name": *"[^"]*"' | awk -F'"' '{print $4}' | sort -V
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 59178    0 59178    0     0   101k      0 --:--:-- --:--:-- --:--:--  101k
nightly
v0.11.5

curl -i "https://api.github.com/repos/neovim/neovim/releases?per_page=25" | grep -o '"tag_name": *"[^"]*"' | awk -F'"' '{print $4}' | sort -V
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  370k    0  370k    0     0   305k      0 --:--:--  0:00:01 --:--:--  305k
nightly
stable
v0.10.1
v0.10.2
v0.10.3
v0.10.4
v0.11.0
v0.11.1
v0.11.2
v0.11.3
v0.11.4
v0.11.5

This PR apparently didn't fix the issue as people still get the error even on latest bob. I'm including myself in "people".

I don't know if this horse is dead, and I'm just kicking it; but I'll also assert we need a different fix. The main issue is that there is no way to know how many items need to be in a page in order to go back far enough to get all the releases we need. If there are more than n nightly releases since the last stable release, it will get buried. We can, however, specify the stable tag in the GitHub API call. As the function is called search_stable_version, I'm guessing it would be better/safer to change the URL called to:

https://api.github.com/repos/neovim/neovim/releases/stable

Then if we want other releases, too, we can do a separate call to get them.

Alternatively we could just get more pages from the existing URL until we get to the stable release.

Thoughts?

@huntwj - temp fix in #360 and refactor proposed, and currently being worked on via Issue #348 and the soon(tm) linked PR that will address it.

Given consistent requests, I'm also going to further open discussion in 348 regarding the ability to use the archive repo that the Neovim org maintains as a host address (for distros that use much older glibc versions for instance)