Skip to content
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.

Sign up for GitHub

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

Jump to bottom

build(deps): bump github.com/operator-framework/operator-registry v1.39 to v1.41 #3256

Merged
merged 1 commit into from
May 16, 2024
Merged

build(deps): bump github.com/operator-framework/operator-registry v1.39 to v1.41 #3256

merged 1 commit into from
May 16, 2024

Conversation

perdasilva
Copy link
Collaborator

Description of the change:

Motivation for the change:

Architectural changes:

Testing remarks:

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Bug fixes are accompanied by regression test(s)
  • e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
  • tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
  • Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
  • Docs updated or added to /doc
  • Commit messages sensible and descriptive
  • Tests marked as [FLAKE] are truly flaky and have an issue
  • Code is properly formatted

@perdasilva perdasilva force-pushed the chore/bump/operator-registry branch 3 times, most recently from f67f70c to a451d21 Compare May 15, 2024 17:31
@perdasilva perdasilva changed the title build(deps): bump github.com/operator-framework/operator-registry v1.39 to v1.40 build(deps): bump github.com/operator-framework/operator-registry v1.39 to v1.41 May 15, 2024
@perdasilva perdasilva force-pushed the chore/bump/operator-registry branch 2 times, most recently from 4d5c697 to 72ce770 Compare May 15, 2024 18:17
build(deps): bump github.com/operator-framework/operator-registry v1.…
f4136b8 
…39 to v1.41

Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
@perdasilva perdasilva force-pushed the chore/bump/operator-registry branch from 72ce770 to f4136b8 Compare May 16, 2024 17:04
joelanford
joelanford approved these changes May 16, 2024
View reviewed changes
Copy link
Member

@joelanford joelanford left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 16, 2024
@perdasilva perdasilva added this pull request to the merge queue May 16, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 16, 2024
@perdasilva perdasilva added this pull request to the merge queue May 16, 2024
Merged via the queue into operator-framework:master with commit d3afe92 May 16, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@joelanford joelanford joelanford approved these changes

@akihikokuroda akihikokuroda Awaiting requested review from akihikokuroda

@dinhxuanvu dinhxuanvu Awaiting requested review from dinhxuanvu

Assignees

@joelanford joelanford

Labels
lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@perdasilva @joelanford