Uh oh!
There was an error while loading. Please reload this page.
OCPBUGS-59518, OCPBUGS-38567: Synchronize From Upstream Repositories - #456
Merged
openshift-merge-bot[bot] merged 95 commits intoSep 5, 2025
Merged
Conversation
Bumps [mkdocs-material](https://github.com/squidfunk/mkdocs-material) from 9.6.17 to 9.6.18. - [Release notes](https://github.com/squidfunk/mkdocs-material/releases) - [Changelog](https://github.com/squidfunk/mkdocs-material/blob/master/CHANGELOG) - [Commits](squidfunk/mkdocs-material@9.6.17...9.6.18) --- updated-dependencies: - dependency-name: mkdocs-material dependency-version: 9.6.18 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [lxml](https://github.com/lxml/lxml) from 6.0.0 to 6.0.1. - [Release notes](https://github.com/lxml/lxml/releases) - [Changelog](https://github.com/lxml/lxml/blob/master/CHANGES.txt) - [Commits](lxml/lxml@lxml-6.0.0...lxml-6.0.1) --- updated-dependencies: - dependency-name: lxml dependency-version: 6.0.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
openshift-ci-robot
commented
Aug 25, 2025
@openshift-bot: This pull request explicitly references no jira issue. 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. |
Contributor
@openshift-bot: GitHub didn't allow me to request PR reviews from the following users: openshift/openshift-team-operator-framework. Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs. 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 kubernetes-sigs/prow repository. |
jianzhangbjz
commented
Aug 26, 2025
Contributor
/unhold |
Bumps [github.com/stretchr/testify](https://github.com/stretchr/testify) from 1.10.0 to 1.11.0. - [Release notes](https://github.com/stretchr/testify/releases) - [Commits](stretchr/testify@v1.10.0...v1.11.0) --- updated-dependencies: - dependency-name: github.com/stretchr/testify dependency-version: 1.11.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [beautifulsoup4](https://www.crummy.com/software/BeautifulSoup/bs4/) from 4.13.4 to 4.13.5. --- updated-dependencies: - dependency-name: beautifulsoup4 dependency-version: 4.13.5 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Adds unit-test/e2e/codecov badges to README.md. The token in codecov is meant to be used by third-parties. Signed-off-by: Todd Short <tshort@redhat.com>
* move crd upgrade safety testdata into crdupgradesafety package Signed-off-by: Joe Lanford <joe.lanford@gmail.com> * fix: bump crdify to fix bugs and regressions regression fixes: 1. correctly handle processing of properties that are OpenAPI items 2. allow enums to have values added. bug fix: crdify's served version validator was updated to actually compare the old CRD with the new CRD so that any issues identified in the old CRD do not continue to be reported when performing comparisons between served versions of the new CRD. This effectively allows issues in the served version validations to be acknowledged once when they are introduced, but then those issues are essentially grandfathered in such that they do not have to be acknowledged again in the future. This issue was actually identified in a case where an operator upgrade was stopped by the CRD upgrade check despite there being no changes whatsoever to the CRD. The "old" and "new" CRDs contained the exact same issues, but since crdify was looking exclusively at the "new" CRD, it found those issues and reported them. --------- Signed-off-by: Joe Lanford <joe.lanford@gmail.com>
tmshort
commented
Aug 26, 2025
Contributor
Keep holding until release-4.20 is cut |
tmshort
commented
Aug 26, 2025
Contributor
/retest |
openshift-botforce-pushed
the
synchronize-upstream
branch
from
August 27, 2025 00:10
0afeadd to
09be1b2Comparejianzhangbjz
commented
Aug 27, 2025
Contributor
Hi @Xia-Zhao-rh , could you help test this PR before merging as it contains operator-framework/operator-controller#2123? Thanks! |
jianzhangbjz
commented
Aug 27, 2025
Contributor
/assign @Xia-Zhao-rh |
Bumps [platformdirs](https://github.com/tox-dev/platformdirs) from 4.3.8 to 4.4.0. - [Release notes](https://github.com/tox-dev/platformdirs/releases) - [Changelog](https://github.com/tox-dev/platformdirs/blob/main/CHANGES.rst) - [Commits](tox-dev/platformdirs@4.3.8...4.4.0) --- updated-dependencies: - dependency-name: platformdirs dependency-version: 4.4.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Xia-Zhao-rh
commented
Aug 27, 2025
Contributor
Test PASS, /label qe-approved |
Xia-Zhao-rh
commented
Aug 27, 2025
Contributor
/retest-required |
openshift-botforce-pushed
the
synchronize-upstream
branch
from
September 4, 2025 18:04
60cc0e0 to
828914cCompare@openshift-bot: This pull request explicitly references no jira issue. 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. |
Contributor
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: anik120, openshift-bot The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
jianzhangbjz
commented
Sep 5, 2025
Contributor
/unhold |
jianzhangbjz
commented
Sep 5, 2025
Contributor
/verified bypass |
openshift-ci-robot
commented
Sep 5, 2025
@jianzhangbjz: The 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. |
jianzhangbjz
commented
Sep 5, 2025
Contributor
/retest-required |
openshift-ci-robot
commented
Sep 5, 2025
Xia-Zhao-rh
commented
Sep 5, 2025
Contributor
Test PASS |
jianzhangbjz
commented
Sep 5, 2025
Contributor
/verified by @Xia-Zhao-rh |
openshift-ci-robot
commented
Sep 5, 2025
@jianzhangbjz: This PR has been marked as verified by 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. |
Contributor
@openshift-bot: 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. |
Uh oh!
There was an error while loading. Please reload this page.
camilamacedo86
commented
Oct 6, 2025
Contributor
/re-title OCPBUGS-59518, OCPBUGS-38567: NO-ISSUE: Synchronize From Upstream Repositories |
camilamacedo86
commented
Oct 6, 2025
Contributor
/retitle OCPBUGS-59518, OCPBUGS-38567: Synchronize From Upstream Repositories |
openshift-ci-robot
commented
Oct 6, 2025
@openshift-bot: Jira Issue OCPBUGS-59518: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-59518 has been moved to the MODIFIED state. Jira Issue OCPBUGS-38567 is in an unrecognized state (Closed) and will not be moved to the MODIFIED state. 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
commented
Oct 8, 2025
Contributor
Fix included in accepted release 4.20.0-0.nightly-2025-10-08-055653 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
18 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The downstream repository has been updated with the following following upstream commits:
The
vendor/directory has been updated and the following commits were carried:This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.
/cc @openshift/openshift-team-operator-framework