Partial channel updates may expose inconsistent dependency states during ros-kilted migrations

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

Hi, I may be misunderstanding part of the intended release flow, but while looking into dependency conflicts during ros-kilted updates, it seems possible for the channel to briefly expose a partially updated platform state.

This does not seem limited to ros2-distro-mutex. Mutex drift looks like one visible symptom, but the broader issue appears to be that many ROS packages have deep dependency relationships, so publishing only part of a platform update may temporarily produce an inconsistent dependency graph for users.

A downstream mitigation I prototyped locally is to add a per-platform release-readiness gate before upload and to support deferred upload in the build scripts. My current assumption is that the cleaner long-term fix is probably upstream in vinca, with ros-kilted keeping a downstream safeguard. If there is already a preferred way to avoid partial platform publication here, I would appreciate guidance.

Installed packages

N/A for local end-user reproduction. This is a repository release-process issue rather than a single local environment issue.

Environment info

Repository: RoboStack/ros-kilted
Branch: main
Context: repository analysis and local prototype work around per-platform release gating

Das Issue nennt keine Dateien oder Tests. Beginne damit, den Release-Ablauf in vinca und die vorhandenen Build-Skripte nachzuverfolgen, und vergleiche dann das vorgeschlagene Gate für die Release-Bereitschaft pro Plattform und das Verhalten bei verzögerten Uploads mit dem Prototyp in ros-kilted. Erledigt ist die Aufgabe, wenn der bevorzugte Upstream- oder Downstream-Ansatz vereinbart ist und eine teilweise Veröffentlichung für Plattformen verhindert wird.