-
Notifications
You must be signed in to change notification settings - Fork 261
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
Upgrading to Eventing sources and messaging latest api version #1160
Comments
@daisy-ycguo Actually, our strategy is a bit more defensive: We want to use the smallest support version of any API right now. The reasoning for this is laid out in #462 |
This issue is stale because it has been open for 90 days with no |
Maybe its a good time now to revisit the eventing API and what we are supporting and whether we need some alignment. Any volunteer to check those API versions ? /remove-lifecycle stale |
This issue is stale because it has been open for 90 days with no |
I think we already updated to the v1 versions where the beta versions were removed, so I'm good with closing this issue. |
Feature request
Eventing has changes their APIs to v1, including:
We may want to support the latest version in Client.
The text was updated successfully, but these errors were encountered: