|
2 | 2 |
|
3 | 3 | All notable changes to this template will be documented in this file. |
4 | 4 |
|
| 5 | +## [v2.0.20260411] - Armored Pangolin - 2026-04-11 |
| 6 | + |
| 7 | +### 🚀 MAJOR RELEASE - V1 → V2 Architecture Transition |
| 8 | + |
| 9 | +This represents a fundamental architectural shift from V1 (template validation workflows) to V2 (project development workflows). |
| 10 | + |
| 11 | +### Breaking Changes |
| 12 | +- **Workflow Architecture**: Complete transition from template validation (V1) to project development (V2) |
| 13 | +- **CI/CD Pipeline**: New comprehensive GitHub Actions workflow replacing template-specific workflows |
| 14 | +- **Branch Structure**: V2/init becomes the new development foundation |
| 15 | +- **Agent Configuration**: Updated agent roles and capabilities for project development |
| 16 | + |
| 17 | +### Security Improvements |
| 18 | +- Enhanced GitHub Actions workflow security with proper permissions blocks |
| 19 | +- Removed risky PIP_USER environment variable from CI/CD pipeline |
| 20 | +- Added secure error handling to shell scripts with 'set -euo pipefail' |
| 21 | +- Implemented job-level permissions for all CI workflow operations |
| 22 | + |
| 23 | +### Infrastructure & DevOps |
| 24 | +- Modernized Docker setup with security-first containerization approach |
| 25 | +- Comprehensive CI/CD pipeline with GitHub Actions integration |
| 26 | +- Improved workflow security following GitHub Advanced Security recommendations |
| 27 | +- Full project development workflow implementation |
| 28 | + |
| 29 | +### Development Experience |
| 30 | +- Complete project-focused development environment |
| 31 | +- Better error handling and security practices in automation |
| 32 | +- Enhanced development workflow with secure defaults |
| 33 | +- Improved CI/CD reliability and security posture |
| 34 | + |
| 35 | +### Migration Notes |
| 36 | +- **BREAKING**: This is a major version requiring migration from V1 template workflows |
| 37 | +- V1 template validation workflows are replaced by V2 project development workflows |
| 38 | +- Projects using V1 should plan migration to V2 architecture |
| 39 | +- All security improvements follow GitHub security best practices |
| 40 | + |
5 | 41 | ## [v1.7.20260410] - Vivid Cardinal - 2026-04-10 |
6 | 42 |
|
7 | 43 | ### Added |
|
0 commit comments