-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
preparing new v3 release #368
Comments
@beriberikix @tim-golioth As we prepare to release version 3, I would like to ask if you have any changes from the API side that need to be made, or if you would be able to contribute some changes, for example #313. |
I don't have anything at the moment. Only thing I had recently was #341 , but that has been approved/merged already. (Note on this one: this PR has a bug in that it looks like the actual code being returned is 4.17, not 4.29. I have a ticket in our backlog to fix this, which I'll be sure to open a PR here as well. Should be able to get it fixed this week.) Let me take a look at #313 and see what's involved. Since this release is targeting 2022.10, it might be something I can take on. |
follow up about the 4.17/4.29 issue: this is a no-op. it was specific to our internal code. nothing related to go-coap. |
v3 main branch
https://github.com/plgd-dev/go-coap/tree/v3
Features:
Optional features:
Release date
2022.10
The text was updated successfully, but these errors were encountered: