neb-helm-release

Orchestrates end-to-end Helm chart release with version bumps and CI validation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-helm-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neb-helm-release
Source: https://github.com/nebinfra/nebcore-ai-skills/tree/main/neb-helm-release
Command: npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-helm-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helm chart releases are complex and error-prone, requiring coordinated updates across submodules, AppSets, and bootstrap configurations. This Skill automates the end-to-end release workflow, reducing manual steps and risk.

Core Features & Use Cases

  • End-to-end release orchestration across submodules and GitOps repos
  • Automatic version bumps, dependency checks, and release metadata updates
  • AppSet synchronization and bootstrap template updates across environments
  • CI validation, ECR publishing verification, and structured PR workflows
  • Use Case: Releasing a library chart propagation across consumers, ensuring dependencies are up-to-date.

Quick Start

Run the neb-helm-release workflow to bump a chart and propagate updates through AppSets and bootstrap files.

Frequently Asked Questions about neb-helm-release

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

FAQPage Schema
How do I automate Helm chart releases across multiple GitOps repos?

Automating Helm chart releases requires orchestrating version bumps, dependency checks, and AppSet synchronization across submodules. This workflow coordinates multi-repo commits via structured PRs to propagate chart updates end-to-end.

How does topological dependency cascading work for library chart updates?

Topological dependency cascading ensures that when a library chart is released, its consumers are automatically identified and updated. The process enforces dependency order, updates helm-charts-releases.yaml, and propagates version bumps across all dependent submodules.

What's the best way to validate AppSet synchronization and bootstrap updates before publishing to ECR?

Validating AppSet synchronization and bootstrap updates requires CI validation checks before ECR publishing. The workflow verifies AppSet configurations, updates bootstrap templates across environments, and ensures all dependencies are met before chart release.

Can I bump Helm chart versions and update bootstrap configurations in a single workflow?

Yes, you can bump chart versions and update bootstrap configurations together. The workflow orchestrates version bumps, AppSet synchronization, bootstrap template updates, and ECR publishing across submodules and GitOps repos in one structured PR workflow.

Why do my Helm chart releases fail when propagating updates to consumer repos?

Helm chart release propagation often fails due to missing dependency checks or unsynchronized AppSets. The workflow enforces topological dependency cascading, validates appsets, and coordinates multi-repo commits to prevent these release errors.

Does neb-helm-release support end-to-end chart releases with ECR publishing and CI validation?

Yes, neb-helm-release supports end-to-end chart releases by orchestrating version bumps, dependency checks, AppSet synchronization, bootstrap updates, CI validation, and ECR publishing across submodules and GitOps repos.