On 15.05.26 at 19:38 (UTC+0200), Robin Candau wrote: > On 5/15/26 6:23 PM, kpcyrd wrote: > > I guess at this point of the integration I would be fine with just > > monitoring the developer dashboard on archlinux.org myself, without > > needing extra emails. That would also solve the problem of stale > > notifications when a co-maintainer updates the package before I even see > > the out-of-date email. When a user explicitly flags I'd be fine with > > receiving one. > > > > [...] > > - Monitoring the developer dashboard on archlinux.org yourself without > opting-in to the notification is indeed a possibility. Alternatively (and > also as a reminder for everyone else reading this mail), bumpbuddy data are > publicly exposed on a web dashboard [3] and as json [4]. The former allows > for a graphical & global monitoring of data with easy filtering (e.g. > searching for your nick in the search bar and sort the "Up to date" column) > and the later can eventually serve as an endpoint for API calls / custom > scripts. >
How often is the out-of-date info updated on archweb? Are there some webhooks set up or does it run a job periodically? In case of the latter, I'd expect a rather long delay between updating a package and clearing the out-of-date flag on archweb, so monitoring the dashboard would not prevent the problem when "a co-maintainer updates the package before I even see the out-of-date package".
signature.asc
Description: PGP signature
