We’re planning for a Humble sync on 2026-03-20T07:00:00Z.
There are currently 2 regressions and 216 packages to release.
We will start holding rosdistro PRs for the sync today (2026-03-17T07:00:00Z) and will plan to do the sync on 2026-03-20T07:00:00Z.
The sync is out!
Hi there! One of the foxglove-bridge maintainers here – just want to check if there’s any way for us to be proactively notified about regressions like this before the sync happens? We only noticed when users started complaining directly to us that the package was no longer in the apt repository and we’ve submitted a fix for the next sync. I believe we receive Jenkins build failure emails, but these tend to be quite noisy and easy to overlook, so I am hoping there is a way we can be notified that “a sync is about to happen and your package is about to be removed unless this is fixed ASAP”? Something like filing a GitHub issue perhaps? Thanks 
I plan to do a sync on Friday: Preparing for Humble sync 2026-03-27
Unfortunately, the best/proper way is the email notifications.
Some time before starting the sync hold, I do indeed sometimes open issues on the corresponding repo to let people know that their package is failing to build, but doing that for every single regressed package build would take a lot of time. Personally, when I see that a package has been failing to build for some time (e.g., a month), I assume it’s just been intentionally ignored.