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

Add guidelines on API version progression to Stable #23

Open
mukundansundar opened this issue Apr 12, 2023 · 0 comments · May be fixed by #24
Open

Add guidelines on API version progression to Stable #23

mukundansundar opened this issue Apr 12, 2023 · 0 comments · May be fixed by #24
Assignees
@mukundansundar

Comments

@mukundansundar
Copy link
Contributor

Following from the discussion in dapr/dapr#5522 (comment) this issue is to add guidelines of when the alpha suffixed HTTP and gRPC API can be removed.

Can/Will v1.0-alpha1 and v1.0 be available for HTTP APIs? Similar question for gRPC. This is make sure that older SDKs are still compatible with newer runtime version of Dapr.
@mukundansundar mukundansundar self-assigned this Apr 13, 2023
@mukundansundar mukundansundar linked a pull request Apr 13, 2023 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mukundansundar mukundansundar

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Api version guide mukundansundar/proposals
1 participant
@mukundansundar