Context

Customers may be confused about the release timing and cadence for UXP (Upbound Crossplane) releases compared to upstream Crossplane releases. They might wonder why downstream UXP releases like v2.2.0-up.1 are not immediately available when the corresponding upstream Crossplane version is released.

Answer

UXP follows a different release cadence than the package policies described for providers and functions. For UXP specifically:

Release Timeline: Upbound typically publishes a new UXP minor version roughly two weeks after the upstream Crossplane release. This delay allows time for additional validation and release preparation.

Additional Validation Steps: Downstream UXP releases go through extended testing and security checks before being published, which can occasionally introduce delays beyond the typical two-week timeframe.

Where to Find Information: The official UXP release cadence is documented at: https://docs.upbound.io/reference/usage/lifecycle/

Important Note: The package policies page at https://docs.upbound.io/manuals/packages/policies/ applies to packages such as providers and functions, and does not apply to UXP releases.

If you notice a UXP release is significantly delayed beyond the expected timeframe, this may be due to internal pipeline issues or extended validation requirements. In such cases, you can contact support for updates on the expected availability.