List of available updates incomplete for "unstable" tree

Hello Michael,

in conjunction with upcoming Core Update 169, I just noticed that my testing machine shows both the Core Update itself and lynis as available updates, but not Tor, which has been recently updated in the "next" branch.

I presume this is due to uploading and/or signing of nightly build packages only performed on a regular interval, not triggered by commits or successful builds. To ensure I am not mistaken on that front, however, I would be glad for a clarification. :-)

All the best, Peter Müller