update-demos

Automating SDK version updates across downstream demo repositories requires coordinating build verification, dependency pin updates, and release runbook generation. This Skill sweeps a registry of buildable projects to ensure compatibility with specific Pulp SDK releases and minimum OS requirements.

Verifying downstream consumer builds against a new SDK release is done through a managed sweep that automatically checks all repositories build correctly against a specific SDK version and reports any minimum OS floor drift.

Yes, bumping dependency pins in demo repos requires Python with PyYAML and access to the Pulp CLI toolchain to execute sweep, update, and publish workflows for the downstream repositories.

Automated dependency pin bumping works by updating SDK version pins across multiple repositories and opening pull requests for review, ensuring all downstream consumer repositories stay synchronized with the latest Pulp SDK release.

Generating release runbooks for rebuilding and publishing demo assets after an SDK update is a core feature that provides a clear, per-repo guide for packaging and publishing once the sweep and pin updates are complete.

Downstream SDK consumer repository lifecycle management is limited to projects registered as buildable within the sweep registry and depends on consistent PyYAML configuration and Pulp CLI toolchain availability to execute workflows without interruption.