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.

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

🌱 Bump operator-registry from v1.46.0 to v1.47.0 #3391

Conversation

perdasilva
Copy link
Collaborator

Description of the change:

Bumps operator-registry to v1.47.0 and with it o-f api to v0.27.0

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

Per Goncalves da Silva added 2 commits September 7, 2024 15:10
@openshift-ci openshift-ci bot requested review from dtfranz and kevinrizza September 7, 2024 13:12
@perdasilva perdasilva changed the title Perdasilva/bump/operator registry 1.47.0 🌱 Bump operator-registry from v1.46.0 to v1.47.0 Sep 7, 2024
@perdasilva perdasilva merged commit b2dd21d into operator-framework:master Sep 7, 2024
12 checks passed
@perdasilva perdasilva deleted the perdasilva/bump/operator-registry-1.47.0 branch September 7, 2024 16:49
@perdasilva perdasilva mentioned this pull request Sep 9, 2024
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant