It wouldn’t be a bad idea to add a canary installation attempt when we push new releases to the bootstrap repository but we don’t have an existing apparatus for doing so which means it’s not a small task to incorporate such a pre-flight check. Because the problem exists only with the release artifacts it’s not something that we could add to the current CI for these projects.
I’ve opened a round of PRs for the other ros-infrastructure packages making sure that they at least have the necessary config values. As our Ubuntu 20.04 environments stabilize these kinds of regressions should dissipate. At least for another two years.