upgrade-guide

Creates step-by-step plans for upgrading Temporal server versions with rollback safeguards.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, safe guide to planning and executing Temporal upgrades, reducing downtime and migration risk.

Core Features & Use Cases

  • Pre-upgrade planning, release-note review, and stakeholder alignment
  • SDK compatibility checks and dependency alignment across client libraries
  • Schema migration guidance and rollback planning, plus health verification
  • Post-upgrade validation and monitoring to ensure cluster health

Quick Start

Ask for a detailed upgrade plan from your current Temporal version to the target version, including rollback steps, schema migrations, and SDK compatibility notes.

Frequently Asked Questions about upgrade-guide

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

FAQPage Schema
How do I plan a safe Temporal server upgrade?

To plan a safe Temporal server upgrade, you need a structured process covering pre-upgrade checklists, version sequencing, SDK compatibility checks, and rollback procedures. This reduces migration risk and downtime across development, staging, and production environments.

What do I need to check before upgrading Temporal to a new version?

Before upgrading Temporal, you must review release notes, align stakeholders, and verify SDK compatibility. Pre-upgrade planning also involves checking dependencies and ensuring your environment is prepared for schema migrations.

Does this Temporal upgrade guide include rollback procedures?

Yes, the Temporal upgrade guide includes detailed rollback procedures and scenarios. It provides structured steps to safely revert your server if issues arise during schema migration or version sequencing.

How do I handle schema migrations during a Temporal upgrade?

Handling schema migrations during a Temporal upgrade requires following specific version sequencing and SDK compatibility checks. The guide provides schema migration guidance to ensure database changes are applied safely without breaking existing workflows.

Can I validate cluster health after completing a Temporal server upgrade?

Yes, you can validate cluster health after a Temporal server upgrade. The guide includes post-upgrade validation and monitoring steps to verify cluster health and ensure the new version operates correctly across all environments.

What is the best way to ensure SDK compatibility when upgrading Temporal?

The best way to ensure SDK compatibility when upgrading Temporal is to perform dedicated compatibility checks and dependency alignment across client libraries. This prevents runtime errors and ensures communication with the upgraded server.