Merge branch 'monthlyupdate' into pipelin-enab

Author: jainyjoseph

src/mas/devops/data/catalogs/v9-260326-amd64.yaml

@@ -13,6 +13,7 @@ ocp_compatibility:
 - "4.18"
 - "4.19"
 - "4.20"
+- "4.21"
 
 # Dependencies
 # -----------------------------------------------------------------------------
@@ -173,4 +174,4 @@ editorial:
     - title: A known issue exists in the January 29, 2026 release affecting HSE and Oil & Gas (9.0.23 / 9.1.64). Customers with HSE installed should avoid upgrading to the January release. Installation of HSE or Oil & Gas on Manage 9.0.x / 9.1.x should be deferred until the February 2026 patch.
     - title: A known issue has been identified in Db2u warehouse operator in this catalog. Customers restoring/upgrading Db2, intermittently get db2 `SQL0290N  Table space access is not allowed.  SQLSTATE=55039` error causing connectivity issue between MAS and Db2. If you are facing this problem, please refer to the workaround provided in this [documentation](https://www.ibm.com/docs/en/cloud-paks/cp-data/5.3.x?topic=SSQNUZ_5.3.x/svc-db2/known-issues-dbs.htm#known-issues-dbs__db2-instance-fails-sql0290n__title__1).
     - title: A known issue exists in the February 26, 2026 release affecting IBM Maximo Real Estate and Facilities. Customers with MREF installed should avoid upgrading to the February 9.1.8 release. Installation of MREF 9.1.x should be deferred until the March 2026 patch.
-    - title: A know issue in IBM Maximo Real Estate and Facilities, users may encounter failures during upgrade scenarios (9.1.x → 9.2 FC) and experience slow installation in airgap environments in the March 26, 2026 release.
+    - title: A know issue in IBM Maximo Real Estate and Facilities, users may encounter failures during upgrade scenarios (9.1.x → 9.2 FC) and experience slow installation in airgap environments in the March 26, 2026 release.

src/mas/devops/data/catalogs/v9-260430-amd64.yaml

@@ -5,7 +5,7 @@
 # catalog itself, but not everything in the catalog supports this yet (including MAS)
 # so we need to use the CASE bundle mirror process still.
 
-catalog_digest: sha256:c852ac109d2a17fab9c58b38389bdf87ed60b9d6273811eb380b8ba2a0c0184f
+catalog_digest: sha256:860184b9e22bd25af3cd1f6ea586a6f6a2c9535f4e58990b317417f53e6de3e2
 
 ocp_compatibility:
 - "4.16"

src/mas/devops/data/catalogs/v9-260430-ppc64le.yaml

@@ -5,7 +5,7 @@
 # catalog itself, but not everything in the catalog supports this yet (including MAS)
 # so we need to use the CASE bundle mirror process still.
 
-catalog_digest: sha256:989162d1f7b519163a7dad9747d78bec0ad05681db396b95f5c9c8fa97ea1d16
+catalog_digest: sha256:05f570d6eb1b44ff4609967e2db306e6208753132bfb7da2f2a90a2d58face85
 
 ocp_compatibility:
 - "4.16"

src/mas/devops/data/catalogs/v9-260430-s390x.yaml

@@ -5,7 +5,7 @@
 # catalog itself, but not everything in the catalog supports this yet (including MAS)
 # so we need to use the CASE bundle mirror process still.
 
-catalog_digest: sha256:bed372211414253afe67ed78a90c3891e002ab8ebddb007050438c94305e940c
+catalog_digest: sha256:4db31da8d274ed24ac5eb558a65d6fe3c3b23238df66192748405ddb0507f542
 
 ocp_compatibility:
 - "4.16"

src/mas/devops/data/ocp.yaml

@@ -9,9 +9,14 @@
 # https://access.redhat.com/support/policy/updates/openshift/
 
 ocp_versions:
+  "4.21":
+    ga_date: "February 3, 2026"
+    standard_support: "GA of 4.22 + 3 Months"
+    extended_support: "N/A"
+
   "4.20":
     ga_date: "October 21, 2025"
-    standard_support: "May 3, 2026"
+    standard_support: "April 21, 2027"
     extended_support: "October 21, 2028"
 
   "4.19":
@@ -21,8 +26,8 @@ ocp_versions:
 
   "4.18":
     ga_date: "February 25, 2025"
-    standard_support: "February 25, 2025"
-    extended_support: "August 25, 2026"
+    standard_support: "August 25, 2026"
+    extended_support: "February 25, 2028"
 
   "4.17":
     ga_date: "October 1, 2024"