Fix invalid olm.skipRange semver in percona-postgresql-operator

[joelanford]

Summary

• Remove v prefix from version in olm.skipRange annotations across 12 CSV versions
• <vX.Y.Z is not valid semver range syntax; the correct form is <X.Y.Z
• Affected versions: 1.4.0, 2.3.1, 2.3.2, 2.4.0, 2.5.0, 2.6.0, 2.6.1, 2.7.0, 2.8.0, 2.8.1, 2.8.2, 2.9.0

[rh-operator-bundle-bot]

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-runbltjd
Start Time: 2026-05-13 13:07:25+00:00

Tasks

Status	Task	Start Time	Duration
✔️	get-pr-number	2026-05-13 13:07:27+00:00	6 seconds
✔️	acquire-lease	2026-05-13 13:07:36+00:00	5 seconds
✔️	set-github-started-label	2026-05-13 13:07:44+00:00	9 seconds
✔️	set-github-status-pending	2026-05-13 13:07:44+00:00	8 seconds
✔️	set-env	2026-05-13 13:07:56+00:00	5 seconds
✔️	clone-repository	2026-05-13 13:08:11+00:00	a minute
✔️	clone-repository-base	2026-05-13 13:08:11+00:00	a minute
❌	detect-changes	2026-05-13 13:09:37+00:00	14 seconds

Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/796d31d93453b077b5f0bca105a8b297

Troubleshooting

Please refer to the troubleshooting guide.

Run /pipeline restart operator-hosted-pipeline in case of pipeline failure to restart a pipeline.

[rh-operator-bundle-bot]

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-runh58nt
Start Time: 2026-05-13 13:18:40+00:00

Tasks

Status	Task	Start Time	Duration
✔️	get-pr-number	2026-05-13 13:18:47+00:00	5 seconds
✔️	acquire-lease	2026-05-13 13:19:02+00:00	5 seconds
✔️	set-github-started-label	2026-05-13 13:19:15+00:00	10 seconds
✔️	set-github-status-pending	2026-05-13 13:19:16+00:00	6 seconds
✔️	set-env	2026-05-13 13:19:44+00:00	4 seconds
✔️	clone-repository	2026-05-13 13:19:55+00:00	a minute
✔️	clone-repository-base	2026-05-13 13:19:56+00:00	a minute
❌	detect-changes	2026-05-13 13:21:40+00:00	14 seconds

Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/57d40042245532cb45d47eb890b19d4f

Troubleshooting

Please refer to the troubleshooting guide.

Run /pipeline restart operator-hosted-pipeline in case of pipeline failure to restart a pipeline.

[tomasbakk]

@joelanford Hello. I noticed that you tried to modify existing bundles, same as in this PRs -> #9686 #9687 It is not possible to edit existing bundles unless you would switch/onboard to FBC - onboarding doc

[joelanford]

I'm from the OLM team, not a persona developer, so I can't make that decision.

I audited all OLM catalogs and noticed this problem with lots of bundles.

We need to update opm validate to reject invalid skip ranges, but we can't do that until all existing issues are fixed.

Otherwise, this catalog will permafail on opm validate when the pipeline updates to use it.

Anything we can do to fix this without forcing the persona folks to adopt FBC quickly?

[tomasbakk]

@joelanford I am afraid that without switching to FBC there is no easy way how to modify existing, released bundles. Since the needed change is part of the CSV metadata and it requires rebuilding the bundle image and releasing it, it is not possible to do it unless they would onboard to FBC.

[github-actions]

This pull request is stale because it has been open for 30 days with no activity.