Hi, i am currently trying do understand why r-ryantm does not create update PRs for portfolio. So the bot does actually get triggered when upstream does create a new release, but then it does not really find an update. (my observation)
When running the updateScript (that i attached the package quite a while ago), it currently does find an update, so my assumption is, that it kind of is working.

The latest logs of r-ryantm are here for the package: https://r.ryantm.com/log/portfolio/2023-11-03.log
There are multiple things confusing me here:
There was no releas of portfolio on the 3rd, but today on the 4th. Repology did update that on 14:45 actual releas was at 9:42 (my timezone https://repology.org/project/portfolio-performance/history & https://github.com/portfolio-performance/portfolio/releases ) As far as i understood nixpkgs-update does react on reading the history. am i right on that?

Beside thath, that on the very first line the version is wrong, that was working according the logs as some point in the past. (portfolio 0 -> 1 vs the actual numbers in the past portfolio 0.64.1 -> 0.64.4)
What i see, when it got the version right it has the github link appended, so what it then triggered by a GH read?

Some time in the past it seemed to have worked (e.G. https://r.ryantm.com/log/portfolio/2023-06-06.log)

Does someone have an idea whats going wrong here or it there actually nothing wrong and i am just to impatient? :(

In reply to @ryantm:matrix.org
0 -> 1 is the fake version numbers it uses when it does an update based on the package having an updateScript