Refresh Python Desktop API SDK for v6 - #11
Merged
Merged
Conversation
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
1 participant
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.
The Python SDK on PyPI is 5.0.0 and its client has no Labels resource, while the current Desktop API serves
GET /v1/labels. I regenerated the client from the current API schema:src/beeper_desktop_api/resources/labels.pynow calls that endpoint, and_client.pyexposes it on both the synchronous and asynchronous clients. The package version moves to 6.0.0 because the generated resource and type shapes also change.The refresh preserves the existing custom-header behavior and asset-serving implementation. I corrected the README's claim that this package has not yet been published to PyPI. I kept the GitHub-release-triggered PyPI publisher rather than replacing it with a generated workflow that lacks the release trigger, and removed CI steps that only uploaded artifacts to Stainless's internal storage. This PR is the code change; PyPI publication still needs the tagged GitHub release after merge.
Tag
@indentto continue the conversation here.