new-release

Coordinate multi-repo Global Hub releases across six repositories with branch and CI updates.

24|39|Updated Jun 17, 2021
One-click install
npx skills add https://github.com/stolostron/multicluster-global-hub --skill new-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-release
Source: https://github.com/stolostron/multicluster-global-hub/tree/main/.claude/skills/new-release
Command: npx skills add https://github.com/stolostron/multicluster-global-hub --skill new-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, bash, sed, awk, make, docker, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the complete end-to-end workflow for cutting a Multicluster Global Hub release across six repositories, including release branch management, OpenShift CI configuration, catalog and bundle updates, and PR creation. It orchestrates a complex, multi-repo release with explicit release branch control to save time and reduce operational complexity.

Core Features & Use Cases

  • End-to-end release orchestration: Coordinates release tasks across main, CI, bundle, catalog, grafana, and postgres-exporter repositories.
  • Two operating modes: CREATE_BRANCHES=true creates new release branches; UPDATE mode (default) updates via PRs.
  • ** Tekton and CI configuration automation**: Generates and updates .tekton/ pipelines, CI configs, and related assets for new releases.
  • PR lifecycle automation: Creates or updates PRs to upstream/main and per-release branches to propagate changes.
  • Version mapping & asset updates: Applies ACM to Global Hub mappings, image tags, and related metadata across repos.

Quick Start

  • To cut a new release: set RELEASE_BRANCH (e.g., release-2.17) and run the orchestration for all repos: RELEASE_BRANCH=release-2.17 ./scripts/cut-release.sh all
  • To create new release branches: CREATE_BRANCHES=true RELEASE_BRANCH=release-2.18 ./scripts/cut-release.sh all

Frequently Asked Questions about new-release

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

FAQPage Schema
How do I automate a release across multiple repositories?

Automate a release across multiple repositories by orchestrating coordinated updates using a release automation script that manages release branches, CI configurations, and PR workflows simultaneously across all target repos. This skill handles the complete end-to-end workflow for cutting releases across six repositories including the main hub, CI, bundle, and catalog repos.

Can I create new release branches and push changes automatically?

Yes, you can create new release branches and push changes automatically by setting CREATE_BRANCHES=true and specifying your RELEASE_BRANCH variable, then running the orchestration script. This mode creates and pushes release branches across all repositories instead of using the default PR-based update approach.

How do I coordinate Tekton pipeline and CI configuration updates for a multi-repo release?

Coordinate Tekton pipeline and CI configuration updates across multiple repositories by running an automated release orchestration that generates and updates .tekton/ pipelines, CI configs, and related assets for new releases consistently across all target repos in a single operation.

What's the difference between creating new release branches versus updating via pull requests?

Creating new release branches (CREATE_BRANCHES=true) generates and pushes branches directly to all repositories, while updating via pull requests (default mode) creates or updates PRs to propagate changes. Choose branch creation for immediate multi-repo updates or PR mode for review workflows before merging.

Does this support releasing to OpenShift repositories and bundle catalogs?

Yes, this automation coordinates releases across OpenShift CI repositories, operator bundle repositories, and operator catalog repositories as part of its multi-repo orchestration. It applies version mappings, image tag updates, and related metadata consistently across bundle, catalog, and OpenShift CI artifacts.