Open ron1 opened 4 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Bug Report
Package server version and olm.version https://github.com/operator-framework/operator-lifecycle-manager/blob/16619cd27fa56af837c26a49ba9badc7b6566fd8/manifests/0000_50_olm_15-packageserver.clusterserviceversion.yaml#L130 should be consistent with the release tag. Currently, the version is consistently one behind the release tag.
Also, directory deploy/upstream/manifests has the same "one version behind the release tag" problem. For release tag 0.13.0, the latest manifests directory is 0.12.0. Likewise, for release tag 0.12.0, the latest manifests directory is 0.11.0. The contents of this directory should be consistent with the release artifacts which is currently not the case.