epic: Atomic Release Pipeline Actions
@aRustyDev is already working on this.
Since Jan 27, 2026.
Assessment
This issue has not been assessed yet.
Description
Overview
Extract atomic release pipeline functionality from helm-charts into reusable composite actions.
Background
The atomic release pipeline in helm-charts (W1 → W2 → W5 → W6) contains generalizable logic for:
- Attestation management (extract, update, verify)
- Atomic branching (detect changes, create branch/PR)
- Version bumping (determine bump type, calculate version)
- Trust validation (source branch, CODEOWNERS)
Goal
Create composable actions that any repo can use to implement an attestation-backed release pipeline.
Action Inventory
Attestation (actions/attestation/)
| Action | Issue | Priority | Status |
|---|---|---|---|
extract-map |
#23 | P0 | 📋 Open |
update-pr-map |
#24 | P0 | 📋 Open |
generate-digest |
#25 | P0 | 📋 Open |
verify-chain |
#26 | P1 | 📋 Open |
Atomic Branch (actions/atomic-branch/)
| Action | Issue | Priority | Status |
|---|---|---|---|
detect-changes |
#27 | P1 | 📋 Open |
create-branch |
#28 | P1 | 📋 Open |
create-pr |
#29 | P1 | 📋 Open |
Version Bump (actions/version-bump/)
| Action | Issue | Priority | Status |
|---|---|---|---|
determine-bump |
#30 | P1 | 📋 Open |
calculate-version |
#31 | P1 | 📋 Open |
update-manifest |
#32 | P2 | 📋 Open |
Source PR (actions/source-pr/)
| Action | Issue | Priority | Status |
|---|---|---|---|
find |
#33 | P2 | 📋 Open |
Trust Check (actions/trust-check/)
| Action | Issue | Priority | Status |
|---|---|---|---|
validate-source-branch |
#34 | P2 | 📋 Open |
Changelog (actions/changelog/)
| Action | Issue | Priority | Status |
|---|---|---|---|
extract-version |
#35 | P2 | 📋 Open |
Implementation Order
Batch 1 - Core Attestation (P0)
- #23 -
attestation/extract-map - #24 -
attestation/update-pr-map - #25 -
attestation/generate-digest
Batch 2 - Atomic Branch (P1)
- #27 -
atomic-branch/detect-changes - #33 -
source-pr/find - #28 -
atomic-branch/create-branch - #29 -
atomic-branch/create-pr
Batch 3 - Version Bump (P1)
- #30 -
version-bump/determine-bump - #31 -
version-bump/calculate-version
Batch 4 - Supporting (P2)
- #26 -
attestation/verify-chain - #32 -
version-bump/update-manifest - #34 -
trust-check/validate-source-branch - #35 -
changelog/extract-version
Related Issues
- #13 - changelog generation (may be consolidated with #35)
- #15 - semver bumping (may be consolidated with #30, #31)
- #18 - W2 change detection (fixed in reusable workflow v0.1.1)
Implementation Notes
- Actions should be pure and composable
- Use shell scripts for portability (no Node.js dependencies where possible)
- Follow GitHub Action best practices for inputs/outputs
- Include README with usage examples
- Dominant language
- Shell
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aRustyDev/gh
-
dependencies github-actions
Difficulty 1/5 Under an hour Newbie friendliness 10/100
-
dependencies github-actions
Difficulty 1/5 Under an hour Newbie friendliness 15/100
-
dependencies github-actions
Difficulty 1/5 Under an hour Newbie friendliness 50/100
-
dependencies github-actions
Difficulty 2/5 1-3 hours Newbie friendliness 20/100
-
dependencies github-actions
Difficulty 2/5 1-3 hours Newbie friendliness 10/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
community-scripts/ProxmoxVE#17425 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
agent-research-recommend agent-review-finding
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jordansmall/spindrift#3714 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
conda-forge/python-feedstock#934 ·