generated from camaraproject/Template_API_Repository
-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Labels
enhancementNew feature or requestNew feature or requestrelease automationRelated to the implementation or introduction of new release automationRelated to the implementation or introduction of new release automationwg managementIndicating issues with repository of the working groupIndicating issues with repository of the working group
Description
Problem description
The Release Automation workflow has been developed and tested. It now needs to be integrated into the camaraproject organization and rolled out to API repositories with proper branch protection, team permissions, and onboarding tooling.
Part of #191 (Develop automation support in support of release management).
Proposed solution
Integration and roll-out across three repositories:
tooling
- Contribute Release Automation workflow — tooling#69, resolved via PR #67 + PR #68
- Create GitHub App and update workflow — tooling#70, done via PR Use GitHub App token for protected branch operations tooling#74, need to be tested in TestRepo (see Create test repository for Release Automation tooling#72)
- Define API repository setup documentation — tooling#71, PR to review: docs: repository setup for 3-ruleset branch protection design tooling#75
- Create test repository and validate E2E — tooling#72
project-administration
- Onboarding campaign workflow — project-administration#132, PR Add release automation onboarding campaign and admin tooling project-administration#134
- Ruleset application script — project-administration#133, PR Add release automation onboarding campaign and admin tooling project-administration#134
Roll-out phases
| Phase | Scope | Validation |
|---|---|---|
| Alpha | Test repository in camaraproject | Full E2E with branch protection |
| RC | Volunteering API repositories | Real release cycles |
| GA | All API repositories | Bulk rollout |
Additional context
Development was done over 50 sessions with comprehensive E2E testing. Regression testing on the upstream branch confirmed zero bugs for a full release lifecycle (issue creation → snapshot → review → merge → publish). See C2 (#354) and C3-C4 (#355) for the workflow component descriptions.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestrelease automationRelated to the implementation or introduction of new release automationRelated to the implementation or introduction of new release automationwg managementIndicating issues with repository of the working groupIndicating issues with repository of the working group