Appearance
Product Release Lifecycle
INFO
This page is updated when a new Yellowbrick minor version is released. Each release's support status is derived from the support policy below.
This page outlines the release lifecycle and version-management policy for Yellowbrick Data Warehouse releases.
Overview
Yellowbrick follows semantic versioning (MAJOR.MINOR.MICRO). Each release level has a defined support window to ensure stability and predictability for platform upgrades.
Support Policy
| Release Type | Format | Support Duration | Description |
|---|---|---|---|
| Major | 7.x.x | 24 months | Significant architectural changes. Sets the foundation for subsequent releases. |
| Minor | 7.X.x | 6 months | Feature enhancements. Follows an upgrade-only path (for example, 7.2 → 7.3) and extends Major support duration. |
| Micro | 7.x.X | Inherited | Bug fixes and security patches. Inherits the End of Support date of the parent Minor version. |
Release Calendar
The following table lists recent Yellowbrick minor versions and their support status. Micro releases (for example, 7.4.2) share the End of Support date of their Minor version.
| Version | Release Date | End of Support | Status |
|---|---|---|---|
| 7.4 | Jan 15, 2026 | Jul 15, 2026 | End of Life |
| 7.3 | Jul 26, 2025 | Jan 26, 2026 | End of Life |
| 7.2 | Apr 29, 2025 | Oct 29, 2025 | End of Life |
| 7.1 | Jan 24, 2025 | Jul 24, 2025 | End of Life |
For Kubernetes version support on cloud deployments (Amazon EKS, Azure AKS, and Google GKE), see Kubernetes Version Support.
Best Practices
- Upgrade planning: Plan upgrades at least 30 days before a Minor version's End of Support date.
- Forward compatibility: Upgrades (for example, 7.2 to 7.3) preserve compatibility; any behavior changes are documented in the release notes. Downgrades are not supported for Minor versions.
- Environment testing: Validate new versions in a non-production environment before applying to production.