Why Old Azure DevOps Releases Survive a Pipeline Cutover
DevOps.com, Friday, September 25th, 2026
Old Azure DevOps Classic releases retain stale configs that can silently undermine a pipeline migration.
The article explains that Azure DevOps Classic releases act as snapshots, freezing task graphs, Helm names, image paths, and variable values at creation time -- so they keep working even after pipeline definitions are updated in a migration cutover.
This creates risk: an old release referencing a retired Helm name with --install could create a new installation instead of updating the current one, leaving orphaned Kubernetes resources.
To fully complete a migration, the author recommends inventorying pre-cutover releases, inspecting their stored tasks and variables rather than trusting current definitions, removing obsolete image repositories, and abandoning stale releases only after testing, since a green deployment alone doesn't prove old paths are dead.