versioning-guide

Guide engineers in implementing safe Temporal workflow versioning with GetVersion.

3|1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/therealbill/mynet --skill versioning-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: versioning-guide
Source: https://github.com/therealbill/mynet/tree/main/timelord/skills/versioning-guide
Command: npx skills add https://github.com/therealbill/mynet --skill versioning-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Temporal workflows often face non-determinism and rollout risk when code changes while executions are active. This guide provides a structured approach to versioning that preserves running workflows while enabling safe upgrades for new ones.

Core Features & Use Cases

  • GetVersion usage to gate changes without breaking existing runs.
  • Backward-compatible migration patterns that allow old and new logic to run concurrently.
  • Deployment strategy and monitoring guidance to ensure safe rollout and quick rollback if issues arise.
  • Reset alternatives to recover stuck or problematic workflows when needed.

Quick Start

Review your workflow's GetVersion gates and implement a versioned branch to safely upgrade workflows.

Frequently Asked Questions about versioning-guide

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

FAQPage Schema
How do I safely update a Temporal workflow without breaking running executions?

To safely update Temporal workflows without breaking running executions, implement versioning using the GetVersion API to gate code changes, allowing old and new logic to run concurrently while preserving active workflow state.

When do I need to use GetVersion for Temporal workflow versioning?

Use GetVersion for Temporal workflow versioning when adding, removing, or modifying activities to prevent non-determinism errors during active executions. It gates changes so existing runs follow old logic while new runs use updated code.

What is the best way to handle Temporal workflow non-determinism during deployment?

Handle Temporal workflow non-determinism during deployment by applying backward-compatible migration patterns with GetVersion gates, following deployment strategy guidance to monitor rollouts and execute quick rollbacks if issues arise.

Can I roll back a Temporal workflow update if the new version causes issues?

Yes, you can roll back a Temporal workflow update if the new version causes issues by following deployment monitoring guidance and utilizing reset alternatives to recover stuck or problematic workflows affected by non-deterministic code changes.

How do I clean up old workflow versions after migrating Temporal executions?

Clean up old workflow versions after migrating Temporal executions by defining exact version numbering requirements and removing GetVersion gates once all active runs complete, ensuring only the new workflow logic remains.

Does Temporal workflow versioning support concurrent execution of different activity versions?

Temporal workflow versioning supports concurrent execution of different activity versions by using backward-compatible migration patterns, allowing old and new logic to run side-by-side safely without disrupting active executions.