-
Notifications
You must be signed in to change notification settings - Fork 72
Updown quarter sync #263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updown quarter sync #263
Conversation
…thub/workflows/release.yaml Signed-off-by: Joe Lanford <[email protected]> Upstream-repository: operator-registry Upstream-commit: a629d38a2273aa0cd43b7f06702c8c631401f30c
Upstream-repository: operator-registry Upstream-commit: 3c2677ea67da9bb96d9f1db9e45dd4e46b81dd8e
Signed-off-by: Daniel Sover <[email protected]> Upstream-repository: operator-registry Upstream-commit: 24e05d164a1ac1874d7dc8954216b35af9631c1e
This PR bumps operator-framework/api to v0.11.0 Signed-off-by: Anik Bhattacharjee <[email protected]> Upstream-repository: operator-registry Upstream-commit: acaac87c522f1826dce8669eb9108ccacc73af75
In PR openshift#888, there's vendoring of the cel-go package, one of which is named "debug" (github.com/google/cel-go/common/debug). Due to the .gitignore file ignoring all [Dd]bug folders, the vendored package isn't being checked in by git, causing the build to fail. This PR removes the instruction to ignore [Dd]bug/ folders. Signed-off-by: Anik Bhattacharjee <[email protected]> Upstream-repository: operator-registry Upstream-commit: 7a09b48dba29e8d063916f276740a1d737b40121
Updating for reader experience. Signed-off-by: Shivkumar13 <[email protected]> Upstream-repository: operator-registry Upstream-commit: 611525be3bd7374d1e55d43c519e5664e0e91c2c
This commit bumps operator-framework/operator-registry requirement go-sqlite3 from v1.10.0 to v1.14.10 Signed-off-by: Noah Sapse <[email protected]> Co-authored-by: Noah Sapse <[email protected]> Upstream-repository: operator-registry Upstream-commit: 4e3865a5cf1a2b1048d3752071ae1e932953f29c
This commit introduces a series of unit tests that ensure that GRPC connections are configurable through the use of the GRPC_PROXY environment variable. Signed-off-by: Alexander Greene <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: a68dc4262ccb41cc6031ab4ef3823f6ce1713036
…r init hooks (#2523) Signed-off-by: Per G. da Silva <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: b414e6e881066115b4c5dc63840e8d47c624a405
Prepend the https://github.com to ensure that markdown rendered links are not resolved as local links. Signed-off-by: timflannagan <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: bfe8f0f5339c03c4f1ac08ca343b0a5ab28a787a
…(#2463) Update any relevant workflows and downgrade the checkouts action from the v2 to v1 version. This change is predicated on the problematic checkouts@v2 behavior that can lead to an increased change of regressing when landing changes to the default branch (e.g. master/main). This is because there's an existing bug in the v2 world where PRs can checkout the wrong HEAD commit, leading to scenarios where you're testing against an out-of-date commit compared to what's in the master branch. A concrete use case is when a PR is opened, and that PR checks out the current HEAD commit from master, and then a change lands in the master branch, and any subsequent workflow retries for that PR will result in that previous HEAD commit being checked out. There are workarounds that exist, like rebasing the existing PR, or like explicitly pointing the ref to the default branch, but this interaction isn't ideal with workflows are triggered on pushes to branches on top of reacting to pull request triggers. The simplest solution is to revert back to the v1 version and find a better longer term solution. Signed-off-by: timflannagan <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: a2142c1c3b38bd7f0d2a6fb57d6ffdf5e5434604
Signed-off-by: timflannagan <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 3f3f00644ca4a50d845db2b97c12afcea56fd5d8
Signed-off-by: Vu Dinh <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 4daeb114ccd56cee7132883325da68c80ba70bed
Run the e2e GitHub workflow against master periodically, twice per day, at 00:30 and 12:30 ET. Signed-off-by: Nick Hale <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 86a7f54652ecb2fdcc40404cb6afa1660f677ef6
Signed-off-by: Alexander Greene <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: c6cc1d7f706d355e34b1fc6523693bc13ceb4650
* Introduce golangci-lint support Introduce a root .golangci-lint.yaml file to the repository. This file is responsible for housing the golangci-lint configuration, and the various aggregate linters that are enabled/disabled. Signed-off-by: timflannagan <[email protected]> * .github/workflows: Run the golangci-lint action during the sanity checks Update the sanity workflow and add the golangci-lint action. Signed-off-by: timflannagan <[email protected]> * Fix linting violations outlined by golangci-lint Signed-off-by: timflannagan <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: b3cded1d82f74feb0879ccc68abc1388c6ca4e70
Signed-off-by: Per G. da Silva <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: bee0b688521e79a1bba8c2b3463a13a33ae7cd59
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: perdasilva The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@perdasilva: The following tests failed, say
Full PR test history. Your PR dashboard. 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/test-infra repository. I understand the commands that are listed here. |
Signed-off-by: timflannagan <[email protected]> Upstream-repository: api Upstream-commit: 4d4ed5a299506cab8898036a873031e6faa4b0fd
Signed-off-by: timflannagan <[email protected]> Upstream-repository: api Upstream-commit: 4d4ed5a299506cab8898036a873031e6faa4b0fd
Signed-off-by: timflannagan <[email protected]> Upstream-repository: api Upstream-commit: 4d4ed5a299506cab8898036a873031e6faa4b0fd
Signed-off-by: timflannagan <[email protected]> Upstream-repository: api Upstream-commit: 4d4ed5a299506cab8898036a873031e6faa4b0fd
Signed-off-by: timflannagan <[email protected]> Upstream-repository: api Upstream-commit: 4d4ed5a299506cab8898036a873031e6faa4b0fd
Signed-off-by: timflannagan <[email protected]> Upstream-repository: api Upstream-commit: 4d4ed5a299506cab8898036a873031e6faa4b0fd
Signed-off-by: timflannagan <[email protected]> Upstream-repository: api Upstream-commit: 4d4ed5a299506cab8898036a873031e6faa4b0fd
Signed-off-by: timflannagan <[email protected]> Upstream-repository: api Upstream-commit: 4d4ed5a299506cab8898036a873031e6faa4b0fd
No description provided.