Product Release & Lifecycle

TigerGraph follows a structured release and support policy to ensure stability for production environments while providing early access to new features.

1. Version Numbering

TigerGraph uses a modified semantic versioning system: Generation . Feature . Maintenance (e.g., 4.2.1)

• Generation: Represents a core architectural shift.
• Feature Version: Introduces new capabilities.
• Maintenance: Focuses on bug fixes and security patches.

2. Release Types

• LTS (Long Term Support): Released approximately once a year. These versions receive 2 years of maintenance (bug fixes) and 1 year of support-only status.
• Non-LTS: Standard feature releases for users who want the latest capabilities. These receive 1 year of maintenance and 1 year of support.

3. Support Tiers

Phase	Maintenance Release	Technical Support
Maintenance Period	Yes	Yes
Support-Only Period	No (Critical patches only)	Yes
End of Life (EOL)	No	Limited

4. Upgrade Policy

TigerGraph strives for backward compatibility within a generation. Upgrading from one feature version to the next (e.g., 4.1 to 4.2) is designed to be a non-breaking process for your GSQL applications.

[!TIP] Always check the Release Notes before an upgrade for "Reserved Words" or "Behavioral Changes" that might affect your existing queries.