Merged
Conversation
Contributor
Author
|
🧪 Testing To try out this version of the SDK: Expires at: Fri, 22 May 2026 10:40:43 GMT |
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
a52438e to
b62ec68
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
b62ec68 to
4762efd
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
4762efd to
3aba587
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
3aba587 to
3c0d36e
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
3c0d36e to
861e353
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
861e353 to
d4e8fe6
Compare
The invite-user snippet intentionally exercises the deprecated `api_tokens.create` method to demonstrate the end-to-end invite flow. Add a targeted pyright ignore so `./scripts/lint` passes cleanly on the repo (was failing on `next`).
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
d4e8fe6 to
2d424e0
Compare
The release skill was inconsistently surfacing doc-comment-only changes (e.g. Terraform description additions, docstring wording updates) as user-facing features in some releases but not others. This led to different release note content between Go and Python SDKs for the same underlying config changes. Add an explicit filter rule to Part 1 generation: skip changes that only modify comments/docstrings/descriptions with no API behavioral change.
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
2d424e0 to
2891e74
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
2891e74 to
c2daffc
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
c2daffc to
613642e
Compare
Add missing *_and_poll wrappers for K8s cluster (create, update, upgrade, delete) and pool (create, resize, delete) operations — sync + async, with RawResponse/Streaming wrappers registered. Addresses GCLOUD2-24866 (Python SDK portion, polling prerequisite). Examples follow in a separate PR.
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
613642e to
5d430f4
Compare
* feat(cloud): add runnable K8s cluster example Cover the full cluster lifecycle against the live API: cluster create/get/list/update/upgrade/delete (with *_and_poll), certificate + kubeconfig retrieval, pool CRUD with resize and quota check, and node listing for both cluster and pool scopes. Addresses GCLOUD2-24866 (Python SDK portion). * feat(cloud/examples): exercise upgrade path in k8s example Pick the penultimate version for cluster creation so an upgrade target is always available, and add a wait_for_cluster_ready helper invoked after upgrade_and_poll — the upgrade task finishes before the cluster itself settles back to Provisioned, so subsequent mutations (e.g. creating a new pool) can otherwise be rejected with "Cluster or pool is not ready".
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
5d430f4 to
2812128
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
2812128 to
17118a5
Compare
pedrodeoliveira
deleted the
release-please--branches--main--changes--next
branch
Contributor
Author
|
🤖 Release is at https://github.com/G-Core/gcore-python/releases/tag/v0.43.0 🌻 |
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.
Automated Release PR
0.43.0 (2026-04-22)
Full Changelog: v0.42.0...v0.43.0
Features
Bug Fixes
Performance Improvements
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