CVP Failing Test Notification - Detect Accidental Unpublishing of Released Operators Test

1. While the test is non-gating as of today, it will become gating starting Feb 14, 2024 blocking your releases if not fixed before that date.

2. When does this test fail? It fails when your operator bundle is using `olm.skipRange` without `spec.replaces` in the bundle CSV. Here's a list of packages[1] that @Nate Marsella found in the index images that have channel heads which will fail the CVP pipeline if run on Feb 14, 2024.

3. How can we fix this? While you don't have to rebuild any already shipped operator bundles, you should add `spec.replaces` to your bundle CSV for any future releases if you intend on using `olm.skipRange`.

4. What if we want to know more about the test or want to intentionally prune the upgrade graph? The answer to this question can be found in this google doc[2]. If you have any further questions, please feel free to contact the CVP team[3].

    1.
    2.
    3.
    

CVP warns of "accidental unpublishing of released operators"

CVP passes without warnings

[1] https://docs.google.com/spreadsheets/d/1EPz_eyFADgiFSZYsJSvGYJBJb03BLOfgW1ykeosYRCs/edit?usp=sharing
[2] https://docs.google.com/document/d/1MF2VQ5qPgVOgiAfp9jKAOiTg_xM9q5zxbYBGwzFtUxI/edit?usp=sharing
[3] https://docs.engineering.redhat.com/display/CVP/Engage+with+the+CVP+team