upgrade

Parse release metadata and migration indices to upgrade Pulp CLI and SDK.

13|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Generous-Corp/pulp --skill upgrade-generous-corp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upgrade
Source: https://github.com/Generous-Corp/pulp/tree/main/.agents/skills/upgrade
Command: npx skills add https://github.com/Generous-Corp/pulp --skill upgrade-generous-corp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the complex process of upgrading the Pulp CLI and SDK, ensuring that users stay current with the latest features while safely navigating breaking changes and configuration migrations.

Core Features & Use Cases

  • Automated Migration Guidance: Detects version skew and provides actionable migration notes for breaking changes in CMake macros, APIs, and config files.
  • Safe SDK Pinning: Manages project-specific SDK versions and provides clear paths for upgrading or unpinning dependencies.
  • Use Case: When a developer bumps their Pulp SDK version, this skill identifies necessary code changes, such as renamed CMake macros or deprecated API calls, and provides the exact grep commands to fix them before they cause build errors.

Quick Start

Ask the assistant to check for available updates and provide migration notes for the current project.

Frequently Asked Questions about upgrade

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

FAQPage Schema
How do I handle breaking changes when upgrading the Pulp CLI and SDK?

To fix deprecated API calls after a Pulp SDK version bump, use automated migration guidance to detect version skew and identify necessary code changes. The skill provides actionable migration notes and exact grep commands to update deprecated calls before they cause build failures.

What is the best way to manage SDK pinning across different Pulp projects?

The best way to manage SDK pinning across Pulp projects is to use automated tools that manage project-specific SDK versions and provide clear paths for upgrading or unpinning dependencies. This ensures safe synchronization across plugin versions and prevents compatibility issues.

Does the Pulp CLI upgrade process validate my system state before applying migrations?

Yes, the Pulp CLI upgrade process validates your system state through diagnostic commands before applying changes. It checks for version skew, verifies configuration integrity, and provides automated remediation steps for any detected API or configuration shifts.

How do I find renamed CMake macros after updating my Pulp SDK?

To find renamed CMake macros after a Pulp SDK update, parse the release metadata to identify breaking changes. The skill detects these macro renames and provides the exact grep commands needed to locate and update them in your project code.

When should I not use automated migration tools for Pulp CLI updates?

You should not use automated migration tools for Pulp CLI updates when your project has heavily customized configurations or deeply pinned legacy SDK versions that require manual review. Always run diagnostic commands first to validate system state and assess the scope of breaking changes.