NO-ISSUE: Update github.com/openshift/assisted-service/api digest to 1ac3a31

[red-hat-konflux]

This PR contains the following updates:

Package	Type	Update	Change
github.com/openshift/assisted-service/api	replace	digest	4577ef6 -> 1ac3a31

---

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.

This PR has been generated by MintMaker (powered by Renovate Bot).

[red-hat-konflux]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 19 additional dependencies were updated
• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.20 -> 1.21
github.com/onsi/gomega	v1.28.1 -> v1.30.0
github.com/openshift/custom-resource-status	v1.1.2 -> v1.1.3-0.20220503160415-f2fdb4999d87
github.com/openshift/hive/apis	v0.0.0-20220222213051-def9088fdb5a -> v0.0.0-20231220215202-ad99b9e52d27
k8s.io/api	v0.28.4 -> v0.29.5
k8s.io/apimachinery	v0.28.4 -> v0.29.5
k8s.io/client-go	v0.28.4 -> v0.29.2
github.com/evanphx/json-patch/v5	v5.7.0 -> v5.8.0
github.com/fsnotify/fsnotify	v1.6.0 -> v1.7.0
github.com/go-logr/logr	v1.2.4 -> v1.4.1
github.com/go-logr/zapr	v1.2.4 -> v1.3.0
github.com/golang/protobuf	v1.5.3 -> v1.5.4
github.com/prometheus/client_golang	v1.17.0 -> v1.18.0
go.uber.org/zap	v1.25.0 -> v1.26.0
google.golang.org/protobuf	v1.31.0 -> v1.33.0
k8s.io/apiextensions-apiserver	v0.28.2 -> v0.29.2
k8s.io/component-base	v0.28.4 -> v0.29.2
k8s.io/klog/v2	v2.100.1 -> v2.110.1
k8s.io/kube-openapi	v0.0.0-20230918164632-68afd615200d -> v0.0.0-20231010175941-2dd684a91f00
sigs.k8s.io/structured-merge-diff/v4	v4.3.0 -> v4.4.1

[openshift-ci-robot]

@red-hat-konflux[bot]: This pull request explicitly references no jira issue.

In response to this:

This PR contains the following updates:

Package	Type	Update	Change
github.com/openshift/assisted-service/api	replace	digest	4577ef6 -> 02b1dc4

---

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.

This PR has been generated by MintMaker (powered by Renovate Bot).

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 openshift-eng/jira-lifecycle-plugin repository.

[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 eranco74 for approval. For more information see the Code Review Process.

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

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 github.com 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.

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.