release: 2.0.0-alpha.29 #80
Closed
+1,251
−35
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
|
🧪 Testing To try out this version of the SDK, run: Expires: Sun, 09 Nov 2025 20:29:27 GMT |
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
6 times, most recently
from
9d8eec8 to
ac919b6
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
ac919b6 to
26c4bfb
Compare
* docs: add migration guide for upgrading from v1 to v2 This PR adds UPGRADING.md, a comprehensive migration guide for users upgrading from the v1 Replicate Python SDK to v2. The guide covers: - Client initialization changes (Replicate vs Client, bearer_token vs api_token) - Prediction lifecycle changes (resource methods vs instance methods) - Async support differences (AsyncReplicate client vs async_ methods) - Error handling improvements (granular exception types) - Pagination enhancements (auto-pagination) - Models and versions API changes (keyword arguments) - File handling differences - New features in v2 (models listing, better types, HTTP customization) - Removed features (instance methods, positional arguments) - Migration strategy recommendations Addresses DP-684 * docs: remove unnecessary implementation detail about Prefer headers * docs: clarify "resource methods" terminology in migration guide * docs: add section links to migration checklist * docs: clarify auto-pagination behavior in v2 * docs: add wait example for trainings to mirror v1 * docs: clarify file upload supports file handles without reading into memory * docs: correct async support in use() interface - v1 also had it * docs: add documentation reference for APIResponse object * fix upgrading note about creating predictions * remove unrelated comment about models.list() * docs: update streaming section to show replicate.use() with streaming=True Update migration guide to reflect that replicate.use() with streaming=True is the preferred approach for streaming in v2. Mention that replicate.stream() still works but is deprecated, without showing a code example. * update client section of upgrade guide * docs: use anthropic/claude-4.5-sonnet in streaming examples * Update UPGRADING.md * Update UPGRADING.md * Update UPGRADING.md
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
26c4bfb to
67fbe9c
Compare
stainless-app
bot
deleted the
release-please--branches--main--changes--next
branch
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
2.0.0-alpha.29 (2025-10-10)
Full Changelog: v2.0.0-alpha.28...v2.0.0-alpha.29
Features
replicate.stream()for v1 compatibility (#79) (79b69bd)Chores
Documentation
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