skills.rest
bethanychamberlain
bethanychamberlainCOMMUNITY
Explore all skills by this author →
GitHub

upgrades

Plan and execute LibreChat upgrades across Docker and Kubernetes deployments.

2|Updated Mar 23, 2026
Search Tags:#rollback#verification#migration#backup#upgrade#breaking-changes#librechat
One-click install
npx skills add https://github.com/bethanychamberlain/claude-skills-librechat --skill upgrades-bethanychamberlain
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: upgrades
Source: https://github.com/bethanychamberlain/claude-skills-librechat/tree/main/librechat-ops/skills/upgrades
Command: npx skills add https://github.com/bethanychamberlain/claude-skills-librechat --skill upgrades-bethanychamberlain

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Upgrading LibreChat is complex and risk-prone, involving data migrations, breaking changes, and potential downtime. This Skill provides a guided, repeatable process to plan, execute, and validate upgrades with safety nets and rollback options.

Core Features & Use Cases

  • Plan upgrades by comparing current and target versions, identifying breaking changes, required migrations, and deprecations.
  • Execute upgrades with built-in backups, staged rollout, and post-upgrade validation to ensure a stable transition.
  • Handle post-upgrade issues with quick recovery steps and a clear rollback path for failed upgrades.
  • Use Case: A team upgrading from v0.7.x to v0.8.x can follow this Skill to coordinate migrations, verify service health, and minimize downtime.

Quick Start

Outline your current LibreChat version, target version, deployment method, and backup status, then start the upgrade workflow.

Frequently Asked Questions about upgrades

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

FAQPage Schema
How do I safely upgrade LibreChat across Docker or Kubernetes deployments?▼

Safely upgrade LibreChat by following a guided workflow that enforces pre-upgrade checks, references official breaking changes, identifies required migrations, and provides step-by-step execution and verification across Docker and Kubernetes deployments.

What should I check before migrating LibreChat to a new version?▼

Before migrating LibreChat, compare your current and target versions to identify required migrations, deprecations, and breaking changes, while ensuring you have a confirmed backup status to prevent data loss during the transition.

Can I rollback a failed LibreChat upgrade if something breaks?▼

Yes, you can rollback a failed LibreChat upgrade using the provided rollback guidance and quick recovery steps, which restore your previous deployment state if post-upgrade validation detects service health issues or breaking changes.

What is the best way to handle breaking changes and deprecations during a LibreChat upgrade?▼

The best way to handle breaking changes and deprecations during a LibreChat upgrade is to reference official upgrade procedures, apply a staged rollout with built-in backups, and coordinate required migrations while validating service health at each step.

Do I need a backup to execute a LibreChat version update?▼

Yes, you need a confirmed backup before executing a LibreChat version update. The upgrade workflow requires outlining your backup status beforehand to ensure data safety and enable a reliable rollback path if the execution fails.

Related Skills

Explore More Software Engineering Skills→
lubusINlubusIN
48

frappe-project-triage

Identify Frappe project type, installed apps, version, and tooling.

Official
Intermediate
CODE-SAURABHCODE-SAURABH
2

land-and-deploy

Merge approved pull requests and verify production health after deployment.

Community
Advanced
justanestajustanesta
2

python-devops-automation

Automate Python-based DevOps tasks for infrastructure, AWS, CLI tools, subprocesses, and containers.

Community
Intermediate
JansenAnalyticsJansenAnalytics
5

migration-planner

Plan framework, language, or API migrations with checklists and rollback plans.

Community
Advanced