Update criteria too restrictive

[ryantm]

1. It wants to see the old version repology says nixpkgs-unstable is at to do an update, so it won't update in the case where someone else has updated the expression on master to a version between the OLD and NEW versions.
2. It wants no branch to exist for updating the package, so it won't do an update if there is a pending PR updating to a version between the OLD and NEW versions.

[layus]

1. could be worked around, because you can reproduce repology version detection locally. Run it for the current package, and use that instead of repology info maybe ?

[sedlund]

noticed this today:

2024-12-26 rbw 1.13.0 released
2024-12-27 nixpkgs-update creates PR for 1.13.0
2024-12-27 rbw 1.13.1 released
2025-01-05 1.13.0 PR merged to master
2025-01-05 build makes it into nixos-unstable-small
2025-01-06 nixpkgs-update sees 1.13.1 is available but does not update as repology says nixos-unstable is still at 1.12.1
2025-01-06 rbw 1.13.2 released