Open sugarraysam opened 2 years ago
Semver is not expected in spec.replaces
or spec.skips
.
Also, this validation logic exists in the operator-framework/api repo. The issue tracking these fixes is: https://github.com/operator-framework/api/issues/226
We'll need to vendor a new version of the api repo in this repo when that fix is released.
I'm confused though, because if you use "v" prefixes in your version, than how would you reference past bundles in spec.replaces
?
Introduction
OPM recently changed their semver package #910. It does not allow the "v" prefix in the CSV version fields. When running bundle validation command, my expectation is that the tooling should detect and failed on invalid semver. This error is unfortunately only catched after an index image is built using the faulty bundle.
The validation should cover all CSV fields where semver are expected:
spec.version
spec.replaces
spec.skips
annotations."olm.skipRange"
Example
I have a local bundle which uses
v1.1.1-57
:OPM version