Advance each service baseline only after its verified deployment

For a selective multi-service release, compare each service with its own last verified deployed revision and advance that baseline immediately after its deployment is confirmed. A single workflow-level success marker can lose changes when an earlier service succeeds and a later service fails; a branch-head comparison can miss changes from skipped or failed releases. Keep missing or non-ancestor baselines conservative so they trigger a build, then use immutable image identity and runtime readiness to decide when a baseline may move. This adds per-service bookkeeping, but avoids silently declaring an incomplete rollout current.

Applies when: A release pipeline independently selects and deploys several services. Keywords: CI selective deployment service baseline partial failure immutable digest GitHub