Epic Goal

• This epic will track the work associated with introducing upgrade edge support and a new way for upgrade edges to be defined implicitly via standard semver semantics.

Why is this important?

• One of the Operator Lifecycle Manager's core value propositions is ensuring that customers upgrade from one version of an operator to another along supported edges.

• In OLM V0, we supported three upgrade edge APIs (replaces, skips, and skipRange) which were used to construct the catalog at build time. Unfortunately, the end-to-end catalog building workflow was relatively confusing to users and changes they made to their catalog often yielded unintended consequences.

Previous Work (Optional):

• Technical Brief
• RFC

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>