One of the most critical aspects of database operations is understanding the support status of your current version. If you’re running CockroachDB, a distributed SQL database, you must stay informed about each version’s EOL (End of Life) and EOS (End of Support) schedules. Continuing to use versions that no longer receive security updates or technical support poses serious risks to your infrastructure.
1. Understanding CockroachDB: Core Concepts and Architecture
CockroachDB is a distributed SQL database developed by Cockroach Labs. Built on a transactional and strongly-consistent key-value store, it ensures scalability and availability in cloud-native environments.
Key features of CockroachDB include:
- Distributed Architecture: Automatically distributes data across multiple nodes
- Automatic Replication and Recovery: Self-healing capabilities during node failures
- SQL Compatibility: High compatibility with existing PostgreSQL applications
- Zero-Downtime Scaling: Scale clusters without service interruption
CockroachDB is available in both Self-Hosted and Cloud service versions, each with different support policies.
2. CockroachDB Release Strategy: Understanding Regular vs Innovation Releases
Since 2024, CockroachDB has adopted a new release strategy, moving from 6-month cycles to 3-month major version releases for faster innovation delivery.
Regular Releases (Required Upgrades)
Regular Releases are mandatory upgrade versions with these characteristics:
- 12 months Maintenance Support: Bug fixes, security patches, and feature enhancements
- 6 months Assistance Support: Critical security fixes only
- LTS Support: Since v23.1, eligible for Long-Term Support designation
- Stability Focus: Thoroughly tested stable features
Innovation Releases (Optional Upgrades)
Innovation Releases are optional upgrade versions offering:
- 6 months Maintenance Support only: No Assistance Support phase
- Feature Priority: Early access to latest capabilities
- Skippable: CockroachDB Standard/Advanced users can skip these releases
- CockroachDB Basic: Automatic upgrades required
3. Version Naming Convention and Support Types
Versioning Scheme
CockroachDB uses Calendar Versioning:
- Format:
vYY.R.PP - YY: Year (e.g., 25 = 2025)
- R: Release number within the year (1, 2, 3, 4)
- PP: Patch number (starting from 0)
Example: v25.2.4 is the fourth patch of the second major release in 2025.
Support Phase Details
Maintenance Support
- Regular patch releases provided
- Critical security fixes applied
- User-reported bug resolutions
- Possible backporting of new version features
- Technical support and workarounds
Assistance Support
- Critical security fixes only
- Feature enhancements discontinued
- Limited bug fix patches
- Upgrade to newer versions recommended
Unsupported
- All technical support discontinued
- Security updates ceased
- No SLA guarantees
4. Complete CockroachDB Version EOL/EOS Schedule
Currently Supported Versions (September 2025)
| Major Version | Release Type | GA Release Date | Maintenance Support Ends | Assistance Support Ends | Latest Patch Version | Current Status |
|---|---|---|---|---|---|---|
| v25.3 | Innovation | 2025-08-04 | 2026-02-04 | N/A | v25.3.2 | ✅ Currently Supported |
| v25.2 | Regular | 2025-05-16 | 2026-05-16 | 2026-11-16 | v25.2.4 | ✅ Currently Supported |
| v24.3 | Regular | 2024-11-18 | 2025-11-18 | 2026-05-18 | v24.3.20 | ✅ Currently Supported |
| v24.1 | Regular | 2024-05-20 | 2025-05-20 | 2025-11-20 | v24.1.22 | ⚠️ Assistance Support |
| v23.2 | Regular | 2023-11-13 | 2024-11-13 | 2025-05-13 | v23.2.27 | ⚠️ Assistance Support |
| v23.1 | Regular (LTS) | 2023-05-15 | LTS Extended Support | LTS Extended Support | v23.1.30 | ✅ LTS Support |
End-of-Life Versions (EOL)
| Major Version | Release Type | GA Release Date | Maintenance Support Ended | Assistance Support Ended | Final Patch Version | EOL Status |
|---|---|---|---|---|---|---|
| v25.1 | Innovation | 2025-02-15 | 2025-08-15 | N/A | v25.1.10 | ❌ EOL (2025-08-15) |
| v24.2 | Innovation | 2024-08-12 | 2025-02-12 | N/A | v24.2.10 | ❌ EOL (2025-02-12) |
| v22.2 | Regular | 2022-12-05 | 2023-12-05 | 2024-06-05 | v22.2.19 | ❌ EOL (2024-06-05) |
| v22.1 | Regular | 2022-05-24 | 2023-05-24 | 2023-11-24 | v22.1.22 | ❌ EOL (2023-11-24) |
| v21.2 | Regular | 2021-11-16 | 2022-11-16 | 2023-05-16 | v21.2.17 | ❌ EOL (2023-05-16) |
| v21.1 | Regular | 2021-05-18 | 2022-05-18 | 2022-11-18 | v21.1.21 | ❌ EOL (2022-11-18) |
Legacy Versions (4+ Years Old, Binaries Unpublished)
| Major Version | Release Type | GA Release Date | Final Patch Version | Binary Status | EOL Date |
|---|---|---|---|---|---|
| v20.2 | Regular | 2020-11-10 | v20.2.19 | 🚫 Unpublished (2024-11-10) | EOL (2021-11-10) |
| v20.1 | Regular | 2020-05-12 | v20.1.17 | 🚫 Unpublished (2024-05-12) | EOL (2021-05-12) |
| v19.2 | Regular | 2019-11-11 | v19.2.12 | 🚫 Unpublished (2023-11-11) | EOL (2020-11-11) |
| v19.1 | Regular | 2019-04-30 | v19.1.11 | 🚫 Unpublished (2023-04-30) | EOL (2020-04-30) |
Early Versions (Semantic Versioning Era)
| Major Version | GA Release Date | Final Patch Version | Binary Status | EOL Date |
|---|---|---|---|---|
| v2.1 | 2018-10-30 | v2.1.11 | 🚫 Unpublished (2022-10-30) | EOL (2019-10-30) |
| v2.0 | 2018-04-04 | v2.0.7 | 🚫 Unpublished (2022-04-04) | EOL (2019-04-04) |
| v1.1 | 2017-10-12 | v1.1.9 | 🚫 Unpublished (2021-10-12) | EOL (2018-10-12) |
| v1.0 | 2017-05-10 | v1.0.7 | 🚫 Unpublished (2021-05-10) | EOL (2018-05-10) |
Critical Notes:
- 🔴 v25.1, v24.2 are already EOL: Immediate upgrade required
- ⚠️ v24.1, v23.2 in Assistance Support: Critical security patches only
- ✅ v25.3, v25.2, v24.3, v23.1(LTS): Safe versions for production use
- 🚫 4+ year old versions: Binaries and Docker images unpublished
5. LTS (Long-Term Support) Significance
LTS Benefits
LTS support introduced with v23.1 is particularly important for enterprise environments:
- Extended Maintenance Support: 1 year from first LTS patch release
- Extended Assistance Support: Additional 1 year after Maintenance Support ends
- Highest Stability: Continuously verified high stability and performance
- Predictable Upgrade Cycles: Easier long-term operational planning
Identifying LTS Versions
LTS versions are designated in official documentation or marked with “LTS” in release notes. Currently, v23.1 is the first LTS version.
6. CockroachDB Cloud vs Self-Hosted: Support Policy Differences
CockroachDB Cloud Support Policy Details
| Service Type | Regular Release Support | Innovation Release Support | Automatic Upgrade Policy | SLA Coverage |
|---|---|---|---|---|
| CockroachDB Basic | 12 months | 6 months | Automatic (Required) | ✅ Supported versions only |
| CockroachDB Standard | 12 months | 6 months | Automatic (Default, can disable) | ✅ Supported versions only |
| CockroachDB Advanced | 12 months | 6 months | Manual (User controlled) | ✅ Supported versions only |
Self-Hosted vs Cloud Comparison
| Aspect | Self-Hosted | CockroachDB Cloud |
|---|---|---|
| Maximum Support | 18 months (Regular Release) | 12 months (All Releases) |
| LTS Support | ✅ Available from v23.1 | ❌ Not available |
| Assistance Support | ✅ Additional 6 months | ❌ None |
| Upgrade Control | Fully manual | Automatic/manual options |
| EOS Notifications | User managed | Automatic 30-day notice |
| SLA Guarantees | User responsibility | Guaranteed for supported versions |
Cloud Service Upgrade Characteristics
CockroachDB Basic
- All major/patch versions automatically upgraded
- Innovation Releases mandatory
- No user control
- Continuous support guaranteed
CockroachDB Standard
- Automatic upgrades by default
- Manual upgrade settings available
- Forced upgrade after 1 year (even with manual setting)
- Innovation Releases optional
CockroachDB Advanced
- Complete upgrade control
- Configurable maintenance windows
- Patch upgrades deferrable for 60 days
- 30-day EOS notifications
Service Selection Guide
| Use Case | Recommended Service | Rationale |
|---|---|---|
| Development/Testing | Basic/Standard | Automatic upgrades for latest features |
| Small Production | Standard | Controlled upgrade timing |
| Enterprise | Advanced | Full control and SLA guarantees |
| Regulated Environments | Self-Hosted | LTS support and extended periods |
7. Practical Upgrade Strategies and EOL Management
Immediate Response Guide by Current Status
🚨 Immediate Upgrade Required (Critical Risk)
| Current Version | Risk Level | Recommended Upgrade Path | Estimated Time |
|---|---|---|---|
| v25.1, v24.2 | ❌ Very High | → v25.3 or v24.3 | 2-4 hours |
| v22.2 and below | ❌ Very High | → v23.1(LTS) → v24.3 | 4-8 hours |
| v20.x and below | ❌ Critical | New cluster + migration | 1-3 days |
⚠️ Planned Upgrade Needed (Caution)
| Current Version | Support Remaining | Recommended Upgrade Timing | Target Version |
|---|---|---|---|
| v24.1 | ~November 2025 | October 2025 | v24.3 or v25.2 |
| v23.2 | ~May 2025 | April 2025 | v24.3 or v23.1(LTS) |
✅ Safe Versions (Recommended)
- v25.3 (Innovation): Supported until February 2026
- v25.2 (Regular): Supported until November 2026
- v24.3 (Regular): Supported until May 2026
- v23.1 (LTS): Extended support
Organizational Upgrade Strategies
Conservative Approach (Enterprise/Financial/Healthcare)
Current: v23.1 (LTS) → Target: v25.2 (Regular) → Next: v27.1 (LTS expected)
- Regular Releases only
- LTS version priority
- 6-month stabilization period
- Skip at least 2 major versions
Balanced Approach (Mid-size/Startups)
Current: v24.3 (Regular) → Target: v25.2 (Regular) → Next: v25.4 (Regular expected)
- Regular Release focus + selective Innovation adoption
- 3-6 month review cycles
- Innovation Release validation in test environments
Aggressive Approach (Development/Testing/Cloud-Native)
Current: v25.3 (Innovation) → Target: v26.1 (Innovation expected) → Continuous latest
- All Release types considered
- 3-month upgrade cycles
- Rapid adoption of new features
- Automated testing environments required
Upgrade Execution Checklist
Pre-Planning Phase (D-7 days)
- [ ] Verify current version EOL date
- [ ] Review target version compatibility matrix
- [ ] Establish backup strategy and test
- [ ] Document rollback scenarios
- [ ] Analyze upgrade impact assessment
Test Environment Validation (D-3 days)
- [ ] Perform staging environment upgrade
- [ ] Application compatibility testing
- [ ] Performance benchmark comparison
- [ ] Backup/restore process validation
- [ ] Monitoring system verification
Production Upgrade (D-Day)
- [ ] Confirm maintenance window timing
- [ ] Prepare traffic distribution and load balancing
- [ ] Execute staged rolling upgrade
- [ ] Real-time monitoring and alerting setup
- [ ] Post-upgrade validation
Automated EOL Monitoring Tools and Scripts
Version Monitoring Script Example
#!/bin/bash
# CockroachDB version and EOL status check script
CURRENT_VERSION=$(cockroach version | grep "Build Tag" | cut -d: -f2 | tr -d ' ')
EOL_CHECK_URL="https://endoflife.date/api/v1/products/cockroachdb/"
echo "Current CockroachDB version: $CURRENT_VERSION"
echo "Checking EOL status..."
# Additional logic for EOL date comparison and notification processing
Regular Review Cycle Recommendations
| Review Frequency | Check Items | Responsible Role |
|---|---|---|
| Weekly | Patch version updates | System Administrator |
| Monthly | EOL approaching versions | Database Administrator |
| Quarterly | Upgrade roadmap review | Architect/Team Lead |
| Semi-annually | Overall version policy review | CTO/Infrastructure Lead |
8. Practical EOL Monitoring and Automation Guide
Official Information Sources and Update Channels
Essential Monitoring Sites
| Site Name | URL | Update Frequency | Usage |
|---|---|---|---|
| CockroachDB Official Releases | releases | Real-time | New version releases |
| Support Policy Page | support-policy | Policy changes | EOL policy updates |
| EndOfLife.date | cockroachdb | Weekly | Quick EOL overview |
| CockroachDB Blog | blog | Irregular | Product roadmap and announcements |
RSS/API Feed Subscription
# iCal feed subscription (calendar apps)
https://endoflife.date/calendar/cockroachdb.ics
# JSON API for automation scripts
https://endoflife.date/api/v1/products/cockroachdb/
Automated EOL Monitoring System Setup
Prometheus + Grafana Metrics Configuration
# prometheus.yml configuration addition
- job_name: 'cockroachdb-eol-check'
static_configs:
- targets: ['localhost:8080']
scrape_interval: 24h
metrics_path: '/metrics/eol-status'
Slack/Teams Notification Automation Script
import requests
import datetime
from dateutil import parser
def check_eol_status():
"""Check CockroachDB EOL status and send Slack notifications"""
response = requests.get('https://endoflife.date/api/v1/products/cockroachdb/')
versions = response.json()
alerts = []
for version in versions:
eol_date = parser.parse(version['eol'])
days_until_eol = (eol_date - datetime.datetime.now()).days
if days_until_eol <= 30:
alerts.append({
'version': version['cycle'],
'days_left': days_until_eol,
'eol_date': eol_date.strftime('%Y-%m-%d')
})
if alerts:
send_slack_alert(alerts)
def send_slack_alert(alerts):
"""Send EOL notification to Slack channel"""
webhook_url = "YOUR_SLACK_WEBHOOK_URL"
message = "🚨 CockroachDB EOL Alert\n\n"
for alert in alerts:
message += f"• v{alert['version']}: EOL in {alert['days_left']} days ({alert['eol_date']})\n"
requests.post(webhook_url, json={'text': message})
Organizational EOL Governance Framework
Role-Based Responsibility Matrix
| Role | Daily | Weekly | Monthly | Quarterly | Annually |
|---|---|---|---|---|---|
| System Administrator | Monitoring | Patch verification | – | – | – |
| DBA | – | EOL status | Upgrade planning | – | – |
| Security Team | – | Vulnerability check | EOL risk assessment | Policy review | – |
| Architect | – | – | Roadmap review | Strategy development | – |
| Management | – | – | – | Budget approval | Strategic direction |
EOL Risk Matrix and Response Plan
| Risk Level | Time Until EOL | Response Action | Escalation |
|---|---|---|---|
| 🔴 Critical | Within 30 days | Immediate upgrade | CTO report |
| 🟠 High | 30-90 days | Upgrade planning | Team lead report |
| 🟡 Medium | 90-180 days | Test environment validation | Weekly review |
| 🟢 Low | 180+ days | Roadmap integration | Monthly review |
Cloud Environment EOL Management Tools
AWS CloudWatch Custom Metrics
# Send CockroachDB version info to CloudWatch
aws cloudwatch put-metric-data \
--namespace "CockroachDB/Version" \
--metric-data MetricName=EOLDaysRemaining,Value=90,Unit=Count
Azure Monitor Log Query
CockroachDBLogs
| where TimeGenerated > ago(1d)
| where LogLevel == "INFO" and LogMessage contains "version"
| summarize count() by Version = extract("v([0-9.]+)", 1, LogMessage)
Google Cloud Monitoring Dashboard
{
"displayName": "CockroachDB EOL Status",
"mosaicLayout": {
"tiles": [{
"width": 6, "height": 4,
"widget": {
"title": "Days Until EOL",
"timeSeriesChart": {
"dataSets": [{
"timeSeriesQuery": {
"prometheusQuery": "cockroachdb_eol_days_remaining"
}
}]
}
}
}]
}
}
Conclusion: Immediate Action Items and Long-term Strategy
Immediate Action Checklist (Today’s Tasks)
Step 1: Current Status Diagnosis (30 minutes)
# Check current version
cockroach version
# Verify cluster-wide node versions
SELECT node_id, address, build_tag FROM crdb_internal.gossip_nodes;
# Immediate EOL status check
Compare your current version against the tables above for risk assessment
Step 2: Immediate Response if Critical (Within 24 hours)
- 🚨 Running v25.1, v24.2: Complete upgrade before Friday
- 🚨 Running v22.2 or below: Emergency upgrade planning this weekend
- 🚨 Running v20.x or below: New cluster setup + data migration planning
Step 3: Monitoring System Setup (This week)
- Subscribe to EndOfLife.date RSS feeds
- Set up CockroachDB EOL bot in internal notification channels
- Schedule monthly version status reports
Long-term Strategy Roadmap by Organization Type
Startups/SMBs (Resource-Constrained)
Goal: Safe operations with minimal resources
Short-term (1-3 months): Apply stable version v24.3 or v25.2
Mid-term (6 months): Build automated EOL monitoring
Long-term (1 year): Evaluate CockroachDB Cloud migration
Mid-size Companies (Growth Phase)
Goal: Balance scalability with stability
Short-term: Regular Release-focused operations
Mid-term: Innovation Release validation process in test environments
Long-term: LTS version-centered predictable upgrade cycles
Enterprise/Financial (Stability First)
Goal: Enterprise-grade stability and compliance
Short-term: LTS version (v23.1) standardization
Mid-term: Internal EOL governance process establishment
Long-term: Self-hosted + 2-year LTS upgrade cycles
2025-2026 CockroachDB Release Calendar and Planning
| Timeline | Expected Release | Type | Recommended Action |
|---|---|---|---|
| November 2025 | v25.4 | Regular | Set as mid-term target version |
| February 2026 | v26.1 | Innovation | Test environment validation only |
| May 2026 | v26.2 | Regular | Production deployment after stabilization |
| August 2026 | v26.3 | Innovation | Skip recommended (most organizations) |
Final Recommendations and Key Messages
Security and stability are non-negotiable. Especially in distributed database environments, continuing to use unsupported versions creates serious security vulnerabilities.
Check now:
- Ensure your current CockroachDB version is in the ✅ safe range from the tables above
- If using v25.1 or v24.2, establish upgrade schedule within this week
- Verify other teams in your organization aren’t exposed to the same risks
Remember:
- Innovation Releases: 6 months support, Regular Releases: 18 months support
- v23.1 is the first LTS version with extended support
- Versions 4+ years old have unpublished binaries
- CockroachDB Cloud has separate support policy (12 months maximum)
With CockroachDB’s powerful distributed architecture and zero-downtime upgrade capabilities, proper planning and preparation enable safe and efficient version management. Start today to protect your organization’s database assets. 🙂