upgrading-chart — Claude Code skill: what it does, how to install
upgrading-chart upgrades PostgreSQL and Vault Helm chart dependencies across Chainloop, blocking any major version changes.
Apache-2.0 1 installs ★ 615 updated 2026-10-29
npx skills add chainloop-dev/chainloop --skill upgrading-chart -a claude-codeWhat upgrading-chart does
This skill automates maintenance for Bitnami postgresql and vault Helm charts inside the Chainloop repository. It operates in two modes: pinning a container image to a specific Bitnami release commit or upgrading to the latest minor chart release while updating vendorized files.
Before modifying files, the skill inspects version and appVersion in Chart.yaml. Major version bumps are forbidden. If the leading version digit changes, execution halts immediately for manual review. Dex is managed separately and skipped by this skill.
Post-upgrade validation relies on helm lint and running Docker Compose in the devel directory.
What it helps with
- upgrade PostgreSQL or Vault Helm charts to the latest minor release
- update Bitnami container image references and workflow commit hashes
- prevent accidental major version breaking changes in vendorized charts
- validate modified Helm templates using
helm lintand local Docker Compose
Example prompts for the agent
- Upgrade the postgresql chart to the latest minor version
- Update the vault container image to the target Bitnami release commit
How to install upgrading-chart
1Skills CLI (Vercel)
npx skills add chainloop-dev/chainloop --skill upgrading-chart -a claude-code2Manually: put the files in place
~/.claude/skills/upgrading-chart/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/upgrading-chart/
1Skills CLI (Vercel)
npx skills add chainloop-dev/chainloop --skill upgrading-chart -a codex2Manually: put the files in place
.agents/skills/upgrading-chart/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add chainloop-dev/chainloop --skill upgrading-chart -a cursor2Manually: put the files in place
.cursor/skills/upgrading-chart/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install chainloop-dev/chainloop .claude/skills/upgrading-chart2Manually: put the files in place
.github/skills/upgrading-chart/SKILL.md1Skills CLI (Vercel)
npx skills add chainloop-dev/chainloop --skill upgrading-chart -a gemini-cli2Platform CLI
gemini skills install https://github.com/chainloop-dev/chainloop --path .claude/skills/upgrading-chartManually: put the files in place
.devin/skills/upgrading-chart/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add chainloop-dev/chainloop --skill upgrading-chart -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about upgrading-chart
How do I install upgrading-chart in Claude Code?
Run npx skills add chainloop-dev/chainloop --skill upgrading-chart -a claude-code.
What does the upgrading-chart skill do?
It coordinates minor upgrades for PostgreSQL and Vault dependencies in Chainloop, updating Chart.yaml, vendorized files, and CI workflows.
Does upgrading-chart allow major version upgrades?
No, major upgrades are blocked by safety checks. If a major version jump is detected, the process stops immediately and requires manual escalation.
Source text
SKILL.md · Apache-2.0
---
name: upgrading-chart
description: Upgrades Helm chart dependencies (PostgreSQL, Vault) in the Chainloop project, including vendorized charts, container images, and CI/CD workflows. Use when the user mentions upgrading Helm charts, Bitnami dependencies, PostgreSQL chart, or Vault chart. CRITICAL - Major version upgrades are FORBIDDEN and must be escalated.
---
# Upgrading Helm Chart Dependencies
This skill automates the upgrade process for Helm chart dependencies in the Chainloop project. Supports PostgreSQL and Vault (both Bitnami charts).
## CRITICAL RESTRICTIONS
**Version Upgrade Rules**:
- Patch upgrades (1.2.3 → 1.2.4): ALLOWED
- Minor upgrades (1.2.x → 1.3.x): ALLOWED
- Major upgrades (1.x.x → 2.x.x): **FORBIDDEN - STOP IMMEDIATELY**
**MANDATORY**: If major version upgrade is detected, STOP the process and inform the user that manual review is required.
## Upgrade Types
The skill supports two upgrade types:
1. **Specific Image Upgrade**: Update container image to specific version (chart unchanged)
2. **Chart Minor Version Upgrade**: Update chart to latest minor version (may include image updates)
**IMPORTANT**: Container images are ONLY updated as part of chart upgrades, never independently (unless Type 1).
## Process
### 1. Identify Upgrade Type
Ask the user which type of upgrade they want:
- Type 1: Specific image version upgrade
- Type 2: Latest minor chart version upgrade
Also ask which chart: `postgresql` or `vault`
### 2. Pre-Upgrade Validation
Check current state:
```bash
cat deployment/chainloop/charts/<chart-name>/Chart.yaml | grep "^version:"
cat deployment/chainloop/charts/<chart-name>/Chart.yaml | grep "^appVersion:"
```
### 3. Version Compatibility Check
For any version change, validate that major version remains the same:
```bash
CURRENT_MAJOR=$(echo "$CURRENT_VERSION" | cut -d. -f1)
TARGET_MAJOR=$(echo "$TARGET_VERSION" | cut -d. -f1)
if [ "$CURRENT_MAJOR" != "$TARGET_MAJOR" ]; then
echo "FORBIDDEN: Major version upgrade detected"
exit 1
fi
```
If major version upgrade detected, STOP and escalate.
## Type 1: Specific Image Upgrade
See [image-upgrade-process.md](image-upgrade-process.md) for detailed steps.
**Summary**:
1. Locate target container image in [Bitnami Containers](https://github.com/bitnami/containers)
2. Find commit with release message pattern
3. Extract APP_VERSION from Dockerfile
4. Update `deployment/charts/<chart-name>/Chart.yaml` appVersion
5. Update `.github/workflows/build_external_container_images.yaml` commit hash
## Type 2: Chart Minor Version Upgrade
See [chart-upgrade-process.md](chart-upgrade-process.md) for detailed steps.
**Summary**:
1. Locate target chart version in [Bitnami Charts](https://github.com/bitnami/charts) CHANGELOG.md
2. Validate minor version upgrade only
3. Download and extract target chart
4. Check for image changes (compare Chart.yaml)
5. If images changed, update container image references
6. Vendorize chart update (copy files)
7. Update dependencies in correct order
8. Update main chart dependency version
9. Clean up temporary files
## Verification
After any upgrade type, run:
```bash
# Lint charts
helm lint deployment/charts/<chart-name>
helm lint deployment/chainloop
# Template validation
helm template deployment/charts/<chart-name>
helm template deployment/chainloop
# Local testing
cd devel && docker compose up
# Verify image consistency
grep -r "appVersion\|image.*tag" deployment/charts/<chart-name>/
```
## Files Modified
See [files-modified.md](files-modified.md) for complete list.
## Troubleshooting
Common issues:
- **Image Version Mismatch**: Verify APP_VERSION matches Chart.yaml appVersion
- **Build Failures**: Check commit reference in build workflow
- **Dependency Conflicts**: Verify dependencies updated in correct order (vendorized first, then main chart)
## Rollback
If issues occur:
```bash
git checkout HEAD -- deployment/
find deployment/ -name "Chart.lock" -delete
cd deployment/chainloop && helm dependency build
cd ../../devel && docker compose down && docker compose up
```
## Important Notes
- Dex is self-managed and follows a separate process (not covered by this skill)
- Always use commit hashes for reproducibility
- Dependencies must be updated in correct order: vendorized chart first, then main chart
- Container images are found in Bitnami Containers repo, charts in Bitnami Charts repo
© chainloop-dev · Apache-2.0 · chainloop-dev/chainloop