Merged
Conversation
WilliamTakeshi
approved these changes
Mar 11, 2026
Member
Author
|
-rc1 looks fine (actual README, links and metadata!) and passed all tests of aiocoap from the published version. I can't just tag the same files as release version (for the version is in the names), but will do a quick change-merge-publish cycle without any other changes. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upcoming changes for PSK (starting at #406) will change the Python API.
A 0.6.1 release should get updates to tooling (building on 3.14) and give users a good baseline for that upgrade.
Given that I haven't done any Python release using this crate's tooling, I'm going for an -rc1 so far. Once this PR is approved, I'll start adding a tag to let the actions run through; if the -rc1 looks fine, I'll do a 0.6.1 that is otherwise unmodified.
There is no underlying
lakersrelease, and I think that's fine, as most changes were Python related, and the non-Python changes were just pure refactoring.