Update module github.com/openshift-online/ocm-api-model/clientapi to v0.0.449

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/openshift-online/ocm-api-model/clientapi	v0.0.440 -> v0.0.449

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Release Notes

openshift-online/ocm-api-model (github.com/openshift-online/ocm-api-model/clientapi)

v0.0.449: Release 0.0.449

Compare Source

0.0.449 Feb 11 2026

Add upgrade policies resources for both control plane and node pool for ARO-HCP

• Add ControlPlaneUpgradePolicies resource to manage control plane upgrade policies
• Add NodePoolUpgradePolicies resource to manage node pool upgrade policies
• Simplify upgrade policy types by removing scheduling-related fields (Schedule, ScheduleType, UpgradeType, NextRun, EnableMinorVersionUpgrades)

v0.0.448: Release 0.0.448

Compare Source

• Add VnetIntegrationSubnetResourceID field to ARO-HCP Azure type for SWIFT
  networking (Azure Container Networking Interface) support
• Expose ARO-HCP cluster's provision shard subresource GET endpoint
• Expose ARO-HCP provision shard global endpoints

v0.0.447: Release 0.0.447

Compare Source

• Make Topology attribute of ARO-HCP ProvisionShard required and restrict
  its allowed value to shared

v0.0.446: Release 0.0.446

Compare Source

• Release just to bump the git tags. goproxy cached the previous tag and did
  not recognize changes after refresh of the tag

v0.0.445: Release 0.0.445

Compare Source

• Add AzureShard and ProvisionShardMaestroConfig to ARO-HCP ProvisionShard
  type
• Remove HypershiftConfig, ManagementCluster, HiveConfig,
  AWSAccountOperatorConfig, GCPProjectOperator, AWSBaseDomain, AWSBaseDomain
  from ARO-HCP ProvisionShard type

v0.0.444: Release 0.0.444

Compare Source

• Add ExcludedNamespaceSelectors to ingress type

v0.0.443: Release 0.0.443

Compare Source

• Add Channel field to Cluster type for Y-stream update channel management

v0.0.442: Release 0.0.442

Compare Source

• Exposed new endpoints: /deleted_clusters, and /deleted_clusters/{deleted_cluster_id}
• Added DeletedCluster model to support requests to the deleted_cluster endpoint.

v0.0.441: Release 0.0.441

Compare Source

• Add cloud_provider field to CS dns_domains type

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux[bot]
Once this PR has been reviewed and has the lgtm label, please assign gdbranco for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.