---
id: SAIFTRBL0011
moved_from:
  - guides/troubleshooting/saif-publish-pipelines-not-created.md
title: saif publish does not create Azure DevOps pipelines for a new or renamed repo
description: An outdated saif CLI silently fails to create pipelines because of a breaking Azure DevOps API change; updating the CLI and re-running saif publish fixes it.
tags:
  - troubleshooting
  - cli
  - pipelines
---

# saif publish does not create Azure DevOps pipelines for a new or renamed repo

**One-sentence summary:** an outdated `saif` CLI silently fails to create the Azure DevOps pipelines during `saif publish` because of a breaking change in the Azure DevOps APIs; update the CLI and re-run `saif publish`.

---

## 🚨 Symptom

After publishing a new (or refactored/renamed) repository, no pipelines appear for it under the project's Pipelines view (`https://dev.azure.com/<org>/<project>/_build?view=folders`). The `saif publish` command itself reports success, with no visible error about pipeline creation.

---

## 📌 Applies to

| Aspect | Value |
| ------ | ----- |
| **Component** | `saif` CLI, Azure DevOps pipeline creation |
| **Forge versions** | `saif` CLI 3.8.4 and earlier |
| **Related versions** | Fixed by updating to the latest `saif` CLI; check the [version compatibility matrix](../reference/version-compatibility.md) |

---

## 🧠 Cause

Azure DevOps changed its APIs in June in a way that broke Microsoft's own client library that `saif` depends on for pipeline creation. Any `saif` CLI version released before that fix was picked up (3.8.4 and earlier) can publish the repository itself successfully but fails to create the corresponding pipelines, without surfacing a clear error to the user.

---

## ✅ Fix

1. Update the `saif` CLI to the latest version.
2. Re-run `saif publish` from the repository root:

    ```powershell
    saif publish
    ```

If the repository's git remote was already created by an earlier `saif publish` attempt, re-running may report a git remote URL conflict — see [saif publish fails with "Remote 'origin' already exists with different URL"](saif-publish-remote-origin-url-mismatch.md) if that happens.

---

## 🔬 Verify

The pipelines for the repository now appear under `https://dev.azure.com/<org>/<project>/_build?view=folders`.

---

## 📚 Related

- [saif publish fails with "Remote 'origin' already exists with different URL"](saif-publish-remote-origin-url-mismatch.md)