forked from Hithomelabs/CFTunnels
128 lines
3.2 KiB
Markdown
128 lines
3.2 KiB
Markdown
---
|
|
name: Emergency Rollback Request
|
|
about: Request emergency rollback of OpenRewrite dependency updates
|
|
title: '[ROLLBACK] Emergency rollback request'
|
|
labels: ['rollback', 'urgent', 'dependencies']
|
|
assignees: ''
|
|
|
|
---
|
|
|
|
## Rollback Request
|
|
|
|
### 🚨 Emergency Information
|
|
- **Date of update**: [Date when updates were applied]
|
|
- **PR/Commit**: [Link to problematic update]
|
|
- **Target branch**: [test/main/other]
|
|
|
|
### 📋 Issue Description
|
|
Please provide a detailed description of the issue caused by the OpenRewrite updates:
|
|
|
|
- [ ] Build failures
|
|
- [ ] Test failures
|
|
- [ ] Runtime errors
|
|
- [ ] Performance degradation
|
|
- [ ] Security vulnerabilities
|
|
- [ ] Other (please specify)
|
|
|
|
### 🔧 Error Details
|
|
**Error Messages:**
|
|
```
|
|
Paste relevant error messages here
|
|
```
|
|
|
|
**Stack Trace:**
|
|
```
|
|
Paste stack traces here
|
|
```
|
|
|
|
### 🎯 Affected Components
|
|
- [ ] Application startup
|
|
- [ ] API endpoints
|
|
- [ ] Database connectivity
|
|
- [ ] OAuth2 authentication
|
|
- [ ] Cloudflare API integration
|
|
- [ ] Docker deployment
|
|
- [ ] Other (please specify)
|
|
|
|
### 📊 Impact Assessment
|
|
**Severity:**
|
|
- [ ] Critical (production down)
|
|
- [ ] High (major functionality broken)
|
|
- [ ] Medium (partial functionality broken)
|
|
- [ ] Low (minor issues)
|
|
|
|
**Users Affected:**
|
|
- [ ] All users
|
|
- [ ] Subset of users (please specify)
|
|
- [ ] No users (preventative)
|
|
|
|
### 🔄 Rollback Request
|
|
**Rollback Version:**
|
|
- Target tag/version: [Specify version to rollback to]
|
|
|
|
**Rollback Scope:**
|
|
- [ ] Full dependency rollback
|
|
- [ ] Partial rollback (specify dependencies)
|
|
- [ ] Configuration only
|
|
- [ ] Both dependencies and configuration
|
|
|
|
### 🚀 Urgency
|
|
**Timeline:**
|
|
- [ ] Immediate (within 1 hour)
|
|
- [ ] High priority (within 4 hours)
|
|
- [ ] Normal priority (within 24 hours)
|
|
- [ ] Low priority (within 48 hours)
|
|
|
|
**Production Impact:**
|
|
- [ ] Yes, production is affected
|
|
- [ ] No, staging only
|
|
- [ ] Unknown
|
|
|
|
### 📝 Additional Notes
|
|
Any additional information that would help with the rollback process:
|
|
|
|
- Steps already attempted:
|
|
- Available rollback points:
|
|
- Special considerations:
|
|
- Team notification requirements:
|
|
|
|
### ✅ Checklist Before Submitting
|
|
- [ ] I have checked for existing rollback requests
|
|
- [ ] I have included all relevant error messages
|
|
- [ ] I have specified the target rollback version
|
|
- [ ] I have assessed the impact on users
|
|
- [ ] I have notified relevant team members
|
|
|
|
---
|
|
|
|
## Rollback Process
|
|
|
|
Once submitted, the rollback process will follow these steps:
|
|
|
|
1. **Immediate Assessment** (within 15 minutes)
|
|
- Verify rollback request details
|
|
- Check for conflicting issues
|
|
- Assess rollback feasibility
|
|
|
|
2. **Rollback Execution** (based on urgency)
|
|
- Create rollback branch
|
|
- Revert dependencies/changes
|
|
- Update Docker images
|
|
- Deploy rollback version
|
|
|
|
3. **Validation** (after rollback)
|
|
- Verify functionality restored
|
|
- Run full test suite
|
|
- Monitor production metrics
|
|
- Update documentation
|
|
|
|
4. **Post-Rollback Review**
|
|
- Root cause analysis
|
|
- Update safety procedures
|
|
- Review OpenRewrite configuration
|
|
- Update rollback procedures
|
|
|
|
### 🔔 Notifications
|
|
- Gitea issue updates will be sent automatically
|
|
- Team members will be notified based on urgency level
|
|
- Rollback status will be updated in real-time |