Epic Goal

Before cutting an OCP release, ensure all projects are updated and aligned with the correct Golang and Kubernetes versions for the target release.
All edge dependencies must be updated to avoid CVEs and must match properly released upstream versions.

Downstream projects must:

• Use the correct edge version of OCP APIs and dependencies

• Match the Kubernetes version of the target OCP release

• Use release-specific images for catalog default tests and related projects

• Ensure OLMv0 and OLMv1 are updated and configured to use images from the correct OCP release

Why is this important?

• Prevent CVEs and security risks before release

• Ensure consistency across upstream and downstream projects

• Avoid last-minute release blockers caused by version mismatches

• Guarantee OLM, catalogs, and APIs behave correctly for the target OCP release

Scenarios

• A project is still using an older Golang or Kubernetes version

• Edge dependencies include known CVEs

• Catalog tests run using images from a different OCP release

• OLMv0 or OLMv1 points to incorrect or outdated images

• Downstream builds are not aligned with upstream releases