From 4b6110aed5721408d7c540d2856e928b86cb9d8e Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Wed, 17 Aug 2022 21:03:07 -0700 Subject: [PATCH] core-services/jira-lifecycle-plugin: Allow 4.11.z dependents for 4.10.z bugs Avoid [1]: ... expected dependent Jira Issue OCPBUGS-232 to target a version in 4.11.0, but it targets "4.11.z" instead... Now that 4.11 is GA, 4.10.z backports can carry back both changes that landed pre-GA (4.11.0) and post-GA (4.11.z). Follows up on 8276887da5 (jira-lifecycle-plugin: update target version for 4.11 (#31412), 2022-08-17). [1]: https://github.com/openshift/cluster-version-operator/pull/824#issuecomment-1219003529 --- core-services/jira-lifecycle-plugin/config.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/core-services/jira-lifecycle-plugin/config.yaml b/core-services/jira-lifecycle-plugin/config.yaml index 55da5d6e0bd7f..e62e97fcff672 100644 --- a/core-services/jira-lifecycle-plugin/config.yaml +++ b/core-services/jira-lifecycle-plugin/config.yaml @@ -89,6 +89,7 @@ default: openshift-4.10: dependent_bug_target_versions: - 4.11.0 + - 4.11.z target_version: 4.10.z validate_by_default: true openshift-4.11: