Downstream Release Propagation#
When a producer cuts a release, every dependent automatically receives a pull request that applies the update — the version bump and the related changes it implies — opened by a delegated cloud agent, then reviewed and merged by a human. No dependent has to notice the release or track the bump by hand.
| Page | Description |
|---|---|
| Spec | Requirements for downstream release propagation — dependents automatically receive a reviewed pull request that applies each producer release. |
| Design | How downstream release propagation is built — an inline notification job that resolves the release and delegates a self-contained prompt to a cloud agent in each dependent. |