OCPBUGS-41642: vendor: Update openshift/api to pick up v4.17 capability sets#9003
OCPBUGS-41642: vendor: Update openshift/api to pick up v4.17 capability sets#9003wking wants to merge 1 commit intoopenshift:release-4.17from
Conversation
openshift-ci-robot
added
jira/severity-important
|
@wking: This pull request references Jira Issue OCPBUGS-41642, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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-robot
added
the
jira/invalid-bug
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/hold We want this to merge after openshift/cluster-version-operator#1087, to avoid accepting capability set strings in install-config validation that the Kube API server will later reject in ClusterVersion validation |
openshift-ci
Bot
added
the
do-not-merge/hold
openshift-merge-robot
added
the
needs-rebase
Catching up with [1], and a backport-ish of 9d1f82a8ec (vendor: Update openshift/api to pick up v4.17 and v4.18 capability sets, 2024-09-12, openshift#9002). Generated with: $ GOPROXY=direct go get github.com/openshift/api@release-4.17 $ go mod tidy $ go mod vendor $ go generate ./pkg/types/installconfig.go $ git add -A go.* vendor data/data/install.openshift.io_installconfigs.yaml all using: $ go version go version go1.23.1 linux/amd64 where GOPROXY=direct avoids a caching delay [2]: I committed a new change (or released a new version) to a repository, why isn't it showing up when I run go get -u or go list -m --versions? In order to improve our services' caching and serving latencies, new versions may not show up right away. If you want new code to be immediately available in the mirror, then first make sure there is a semantically versioned tag for this revision in the underlying source repository. Then explicitly request that version via go get module@version. The new version should be available within one minute. Note that if someone requested the version before the tag was pushed, it may take up to 30 minutes for the mirror's cache to expire and fresh data about the version to become available. If the version is still not available after 30 minutes, please file an issue. This will allow users to use the new capability sets in their install-config YAML. [1]: openshift/api#2023 [2]: https://proxy.golang.org/
wking
force-pushed
the
release-4.17-v4.17-capability-set
branch
from
f58596a to
899467f
Compare
|
@wking: This pull request references Jira Issue OCPBUGS-41642, which is invalid:
Comment DetailsIn response to this:
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-merge-robot
removed
the
needs-rebase
|
/skip |
|
I think Prow won't recover from me accidentally openning with |
|
@wking: This pull request references Jira Issue OCPBUGS-41642. The bug has been updated to no longer refer to the pull request using the external bug tracker. DetailsIn response to this:
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. |
|
@wking: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
|
#9013 avoids the Prow vs. base branch confusion. |
3 participants
Catching up with openshift/api/pull/2023, and a backport-ish of 9d1f82a8ec (#9002). Generated with:
all using:
where
GOPROXY=directavoids a caching delay:This will allow users to use the new capability sets in their install-config YAML.