For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.

View supported versions and their release cycle.

Supported versions

Review information about the support and compatibility of Solo Enterprise for agentregistry.

Support matrix

Review the following information about supported release versions for Solo Enterprise for agentregistry.

Compatibility matrix

Review the following table that shows the compatibility matrix for the different versions of Solo Enterprise for agentregistry with related projects.

Release versioning

Solo Enterprise for agentregistry uses calendar versioning, or calver, (YYYY.MM.micro).

Release cadence

New versions are released as they become available, typically on a weekly basis. Each release follows the calver formatting and increases the micro version by 1.

For example:

• The first release in July 2026 is 2026.7.0.
• The next release in July 2026 is 2026.7.1.
• If the next release still happens in July, then it is 2026.7.2.
• If the next release happens in August, then it is 2026.8.0.
• Once a quarter, a release is marked for long-term support (LTS). The LTS release coincides with the latest release for a brief time, and is pinned to a particular micro version, such as 2026.7.1.
• Bug fixes and CVE patches are suffixed to the LTS release version and do not increase the micro version. For example, a patch for the quarterly LTS release in July 2026 that was released after 2026.7.1 is formatted as 2026.7.1-patch.0, not 2026.7.2.

Release streams

Release streams, sometimes also called channels, give you the flexibility to adopt the latest Solo Enterprise for agentregistry features at your own pace.

Example release scenario

Flip through the following hypothetical release scenarios.

As each new release becomes available, the latest supported version gets updated with the latest features, bug fixes, and CVE patches.

• The latest release is 2026.6.3.
• Older releases no longer have the latest features, bug fixes, and CVE patches.

Once a quarter, a release is designated for long-term support (LTS). This release gets bug fixes until the next LTS release and CVE patches for a year.

• The latest release is 2026.7.1.
• The 2026.7.1-patch.0 release is designated as the first LTS patch off 2026.7.1.
• LTS releases continue to get patches, such as 2026.7.1-patch.1 and 2026.7.1-patch.2.

Each stream gets more releases over time.

• In the latest stream, only the most recent release has the latest features, bug fixes, and CVE patches.
• In the LTS stream, several releases are supported at the same time.
• 2026.7.1-patch.N has the features from July 2026, bug fixes until the 2026.10.3 LTS release, and CVE patches for a year.
• 2026.10.3-patch.N has the features from October 2026, bug fixes until the 2027.1.2 LTS release, and CVE patches for a year.
• 2027.1.2-patch.N has the features from January 2027, bug fixes until the next LTS release, and CVE patches for a year.

Feature maturity

Within a release, individual features might be marked as alpha or beta, based on their maturity level.

To receive feedback and improve functionality for real use cases, these features are often released according to a feature maturity model. As the features are improved and stabilized, they are gradually moved through the stages of alpha, beta, and general availability (GA) support. Review the following table for the comparison points between each stage of feature maturity. To see the maturity of a feature, check the feature’s documentation.

Additional support

Have other questions? Reach out to us on Slack or email sales@solo.io.