Skip to content

Commit 96972f0

Browse files
authored
chore: doc comment the need to keep using blang for version ranges (#1600)
Co-authored-by: Artur Zych <[email protected]>
1 parent 33aae8d commit 96972f0

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

internal/catalogmetadata/filter/successors.go

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,11 @@ func legacySuccessor(installedBundle ocv1.BundleMetadata, channels ...declcfg.Ch
6060
}
6161
}
6262
if candidateBundleEntry.SkipRange != "" {
63+
// There are differences between how "github.com/blang/semver/v4" and "github.com/Masterminds/semver/v3"
64+
// handle version ranges. OLM v0 used blang and there might still be registry+v1 bundles that rely
65+
// on those specific differences. Because OLM v1 supports registry+v1 bundles,
66+
// blang needs to be kept alongside any other semver lib for range handling.
67+
// see: https://github.com/operator-framework/operator-controller/pull/1565#issuecomment-2586455768
6368
skipRange, err := bsemver.ParseRange(candidateBundleEntry.SkipRange)
6469
if err == nil && skipRange(installedBundleVersion) {
6570
return true

0 commit comments

Comments
 (0)