release: 0.6.0#26
Merged
stainless-app[bot] merged 19 commits intomainfrom May 6, 2026
Merged
Conversation
Contributor
Author
|
🧪 Testing To try out this version of the SDK: Expires at: Fri, 05 Jun 2026 04:53:13 GMT |
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
3c58380 to
53abd6b
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
53abd6b to
9eb5212
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
9eb5212 to
3b06375
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
3b06375 to
6de987e
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
6de987e to
2bf19a2
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
2bf19a2 to
911f2e5
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
911f2e5 to
394e77b
Compare
Registering schemas as named top-level models in openapi.stainless.yaml
moved several previously-inline class definitions to their own files:
TaskAdvancedSettings(Param), FullContentSettingsParam, FindAllCandidate,
FindAllCandidateMetrics, FindAllRunStatus, MatchCondition(Param),
TaskRunSourceStats, TaskRunProgress*Event. The old inline names disappeared
from their original modules, which Stainless's breaking-change detector
flagged as removals.
Add deprecated aliases at the original import paths so user code that
referenced these names continues to work:
- types/run_input.py::AdvancedSettings
- types/run_input_param.py::AdvancedSettings
- types/task_run_create_params.py::AdvancedSettings
- types/advanced_extract_settings_param.py::FullContentFullContentSettings
- types/task_run_events_response.py::TaskRunProgressStatsEventSourceStats
- types/beta/task_run_create_params.py::AdvancedSettings
- types/beta/findall_candidate_match_status_event.py::Data
- types/beta/findall_create_params.py::MatchCondition
- types/beta/findall_run.py::{Status, StatusMetrics}
- types/beta/findall_run_result.py::Candidate
- types/beta/beta_extract_params.py::FullContentFullContentSettings
- types/beta/task_run_events_response.py::TaskRunProgressStatsEventSourceStats
- types/beta/task_group.py (new — re-export GA TaskGroup)
The TS SDK already handles this implicitly via namespace declaration
merging; Python has no equivalent so we add the aliases manually.
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
394e77b to
748ec35
Compare
uv.lock was added on the integrated branch but is not produced by codegen and is not referenced by any script, CI, or pyproject.toml. The project's canonical lockfiles are requirements.lock and requirements-dev.lock (managed by rye). Tracking uv.lock made the custom-code diff balloon by ~1.2k lines unnecessarily.
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
748ec35 to
e99006e
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
e99006e to
80656d0
Compare
Pyright's reportUnusedImport flags 'from X import Y as Z' as unused even when Z is intentionally re-exported. Switching to a regular import + a module-level assignment makes the re-export explicit and pyright-clean.
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
80656d0 to
f6b228f
Compare
…hange detection
The script previously treated griffe.Alias as opaque (returning {} members).
This produced false positives for back-compat re-exports — both:
* `from .new_path import NewClass` (Alias)
* `OldName = NewClass` (Attribute with ExprName value)
* `OldName = module.NewClass` (Attribute with ExprAttribute value)
Resolve each to the underlying class and report members from there. Real
breaking changes (class definition removed, attribute deleted from the
target class) are still flagged; false positives from intentional
back-compat aliases are not.
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
f6b228f to
b30186c
Compare
The previous edits introduced two redundant comparisons that pyright's strict mode flags as unreachable. Simplify the loop guard and drop the defensive check on final_target's return type.
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
b30186c to
ef78998
Compare
Pyright (1.1.399) flagged `final is current` after isinstance(current, Alias) as unreachable since final_target returns Object. Just return final_target directly. Mypy flagged the second `next_obj` declaration as a redefinition; drop the type annotation on the rebinding.
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
ef78998 to
7ebdf52
Compare
…eprecated Two related fixes for the breaking-change detector against the pre-0.6.0 baseline: * The new `parallel/types/beta/task_group.py` shim wasn't re-exported from `parallel/types/beta/__init__.py`, so baseline tests doing `from parallel.types.beta import TaskGroup` failed pyright. Add the re-export. * The `beta.taskgroup` resource is now `@deprecated` (we recommend GA), but baseline tests don't have a `# pyright: reportDeprecated=false` marker. Promote the per-file marker to project level — deprecation is a runtime concern, not a type error.
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
7ebdf52 to
a61b60b
Compare
NormallyGaussian
approved these changes
May 6, 2026
Contributor
Author
|
🤖 Release is at https://github.com/parallel-web/parallel-sdk-python/releases/tag/v0.6.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
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.
Automated Release PR
0.6.0 (2026-05-06)
Full Changelog: v0.5.1...v0.6.0
Features
Bug Fixes
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