🌟 [Breaking change]: Unified CI/CD Workflow Configuration#202
Closed
MariusStorhaug wants to merge 2 commits intomainfrom
Closed
🌟 [Breaking change]: Unified CI/CD Workflow Configuration#202MariusStorhaug wants to merge 2 commits intomainfrom
MariusStorhaug wants to merge 2 commits intomainfrom
Conversation
- Phase 0: Research complete (conditional execution, concurrency, authentication) - Phase 1: Design complete (data model, workflow contract, quickstart guide) - Phase 2: Task planning approach documented - Updated agent context with feature information - All constitutional requirements validated
Consolidates separate CI.yml into single workflow.yml with improved efficiency, conditional publishing, and better concurrency management. BREAKING CHANGE: The .github/workflows/CI.yml file has been deleted and its functionality merged into workflow.yml. Consuming repositories must migrate to the new unified workflow structure. - Renamed CI.yml to CI.yml.backup (reference only) - Implemented concurrency groups with auto-cancellation - Added conditional job execution based on PR state - Created comprehensive test suite (52 integration tests, 63 contract tests) - Added migration guide and release notes - Updated documentation with breaking change notice Closes #201
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release Notes: Unified CI/CD Workflow (v4.0.0)
Feature ID: 001-unified-workflow
Release Date: 2025-10-02
Type: Breaking Change
Summary
The
CI.ymlandworkflow.ymlfiles have been consolidated into a single unified workflow file (.github/workflows/workflow.yml). This change simplifies the CI/CD pipeline, reduces duplication, and provides clearer conditional logic for test execution and publishing.Breaking Changes
Removed Files
.github/workflows/CI.yml- Deleted (functionality merged intoworkflow.yml)Migration Required
For Consuming Repositories:
If your repository directly references
CI.yml:CI.ymlto useworkflow.ymlinsteadCI.ymlExample Migration:
Before:
After:
See docs/unified-workflow-migration.md for detailed migration instructions.
What Changed
Unified Workflow Structure
The new unified workflow (
workflow.yml) now handles:Key Features
Single Source of Truth
.github/workflows/workflow.yml)Conditional Publishing
github.event.pull_request.merged == true)Concurrency Groups
${{ github.workflow }}-${{ github.ref }}truefor non-default branches,falsefor mainBeforeAll/AfterAll Test Support
tests/BeforeAll.ps1: Runs once before all test matrix jobstests/AfterAll.ps1: Runs once after all test matrix jobs completeWorkflow Execution Order
Validation Status
✅ All local implementation complete (24/28 tasks)
⏳ Manual validation pending - Requires GitHub Actions environment
Test Results:
Code Quality:
Migration Checklist
For repository maintainers migrating to v4:
CI.ymltoworkflow.ymlCI.yml@v3to@v4in workflow callstests/BeforeAll.ps1andtests/AfterAll.ps1if external test resources neededValidation Steps
Scenario 1: PR Opens → Tests Execute, Publishing Skipped
Scenario 2: PR Updated → Tests Re-Execute, Previous Run Cancelled
Scenario 3: PR Merged → Tests Execute, Publishing Executes
Scenario 4: Test Failure → Workflow Fails, Publishing Skipped
See specs/001-unified-workflow/quickstart.md for detailed validation instructions.
Performance
Documentation
Support
For issues or questions:
Closes #201