migrate-pipeline

Migrate Harness pipelines from v0 to v1 via MCP tooling.

80|16|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/harness/harness-skills --skill migrate-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-pipeline
Source: https://github.com/harness/harness-skills/tree/main/skills/migrate-pipeline
Command: npx skills add https://github.com/harness/harness-skills --skill migrate-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrates Harness pipelines from v0 to v1 in a simplified, MCP-driven workflow, ensuring expressions are transformed, types are normalized, and structure is preserved for safe upgrades.

Core Features & Use Cases

  • Migrate pipelines from v0 to v1 using the MCP v2 server.
  • Convert angle-bracket expressions to the ${ { } } syntax and normalize type names.
  • Preserve variables, failure strategies, and conditional logic during upgrade and comparison use cases.

Quick Start

Invoke the migrate-pipeline skill to upgrade a v0 pipeline to v1 using MCP tooling.

Frequently Asked Questions about migrate-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Harness pipelines from v0 to v1?

To migrate Harness v0 pipelines to v1, the skill uses MCP tooling to transform angle-bracket expressions into ${{ ... }} syntax and normalizes type names for the v1 format.

Does migrating v0 to v1 pipelines preserve variables and failure strategies?

Yes, the v0 to v1 migration process preserves variables, failure strategies, and conditional logic during the syntax transformation to ensure the upgraded pipeline structure remains safe and intact.

What is the difference between v0 and v1 pipeline expressions?

The difference between v0 and v1 pipeline expressions is that v0 uses angle-bracket expressions, while the v1 simplified format uses ${{ ... }} syntax and requires type names to be lowercased.

Can I compare v0 versus v1 pipeline formats across different projects?

Yes, you can compare v0 versus v1 pipeline formats across projects and teams, as the MCP tooling applies syntax transformations and allows you to review the upgraded pipeline structure.