Bump cbor2 version#269
Open
typestring wants to merge 3 commits into
Open
Conversation
MasterKale
approved these changes
May 12, 2026
Collaborator
MasterKale
left a comment
MasterKale
left a comment
There was a problem hiding this comment.
Thanks for the PR @typestring, this looks good to me. It's nice to see it's a relatively simple fix to support the latest cbor2 library 😌
And I'm fine with bumping the minimum supported version to 3.10. As per https://devguide.python.org/versions/ it's definitely time to move on from 3.9.
I'm still on parental leave so I can approve and merge but it'll take me a bit to cut a release with this fix. Maybe I can get a release out tonight 🤔
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.
Hi! This PR bumps cbor2 version to address the following CVE: GHSA-3c37-wwvx-h642
This is related to issue #267.
I upgraded to cbor2 v6 and fixed the failing test caused by breaking changes introduced in the new version.
also bumping to v6 requires raising the minimum supported Python version to 3.10. Since Python 3.9 is already EOL, I don’t think this should be a major issue.
If maintaining Python 3.9 support is preferred, an alternative fix would be applying this patch instead: typestring@8385a6a