release: 0.5.2 - #92
Merged
easyCZ merged 2 commits intoDec 17, 2025
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
Author
|
🧪 Testing To try out this version of the SDK, run: pip install 'https://pkg.stainless.com/s/gitpod-python/0cfe207c87e568a6ca9ee6a5ff2251910b064444/gitpod_sdk-0.5.1-py3-none-any.whl' Expires at: Thu, 15 Jan 2026 17:22:18 GMT |
Sorry, something went wrong.
easyCZ
enabled auto-merge (squash)
December 17, 2025 08:14
easyCZ
approved these changes
Dec 17, 2025
Copy link
Copy Markdown
Contributor
Author
|
🤖 Release is at https://github.com/gitpod-io/gitpod-sdk-python/releases/tag/v0.5.2 🌻 |
Sorry, something went wrong.
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
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.
Automated Release PR
0.5.2 (2025-12-16)
Full Changelog: v0.5.1...v0.5.2
Chores
This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions