Release SDK updates - #14
Merged
Merged
Conversation
scripts/mock EMBEDDED_SPEC conflict resolved by taking the new gen-head version; tracking file updated accordingly. Stainless-Generated-From: 96ea59d391e721e9f06a0e9f526cf424554a1f5e
autorender-bot
force-pushed
the
stainless/release
branch
from
June 13, 2026 06:16
6fff8f2 to
4daca99
Compare
Stainless-Generated-From: ec3cebf78b5415d4f7970eda786b518f221a2bc5
autorender-bot
force-pushed
the
stainless/release
branch
from
June 29, 2026 17:12
6b3db9c to
1b70be9
Compare
📝 WalkthroughWalkthroughThe Changesv0.2.2 release: tags type expansion and workflow cleanup
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
tests/api_resources/test_uploads.py (1)
80-91: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winKeep coverage for the legacy string form.
This change broadens
tags, but these are still the only end-to-endcreate_from_url(..., tags=...)cases in the provided tests. Replacing the old string fixture with a list drops regression coverage for the existing comma-separated-string contract, so a serializer change could break current callers unnoticed. Please parametrize these tests over both"tag1,tag2"and["tag1", "tag2"].Also applies to: 180-191
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@tests/api_resources/test_uploads.py` around lines 80 - 91, The create_from_url test coverage in tests/api_resources/test_uploads.py only exercises the new list form for tags and drops the legacy comma-separated string contract. Update the affected create_from_url test cases, including test_method_create_from_url_with_all_params and the other referenced upload tests, to be parametrized over both "tag1,tag2" and ["tag1", "tag2"] so the serializer behavior is validated for both inputs.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CHANGELOG.md`:
- Around line 54-99: The CHANGELOG has a duplicated release section for 0.1.0,
which makes the release history ambiguous. Remove the extra 0.1.0 heading/block
so only one release entry remains for that version, keeping the linked compare
header and the existing Features/Bug Fixes/Chores content under the single 0.1.0
section.
---
Outside diff comments:
In `@tests/api_resources/test_uploads.py`:
- Around line 80-91: The create_from_url test coverage in
tests/api_resources/test_uploads.py only exercises the new list form for tags
and drops the legacy comma-separated string contract. Update the affected
create_from_url test cases, including
test_method_create_from_url_with_all_params and the other referenced upload
tests, to be parametrized over both "tag1,tag2" and ["tag1", "tag2"] so the
serializer behavior is validated for both inputs.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 803ffd6c-f139-4834-8be9-e532510d322a
📒 Files selected for processing (8)
.github/workflows/stlc-promote.yml.github/workflows/stlc-sync-from-production.ymlCHANGELOG.mdpyproject.tomlscripts/mocksrc/autorender/resources/uploads.pysrc/autorender/types/upload_create_from_url_params.pytests/api_resources/test_uploads.py
💤 Files with no reviewable changes (2)
- .github/workflows/stlc-promote.yml
- .github/workflows/stlc-sync-from-production.yml
Comment on lines
+54
to
+99
| ## [0.1.0](https://github.com/autorenderhq/autorender-python/compare/v0.0.1...v0.1.0) (2026-05-25) | ||
|
|
||
|
|
||
| ### Features | ||
|
|
||
| * add test CI job ([2c25e3a](https://github.com/autorenderhq/autorender-python/commit/2c25e3ad8ffe7ff44d5e7781e37de7c2598550df)) | ||
| * **api:** api update ([84d1942](https://github.com/autorenderhq/autorender-python/commit/84d19422bdd7a80d8c0d52fe6bb0e989f7b2abe7)) | ||
| * **api:** api update ([9dc8482](https://github.com/autorenderhq/autorender-python/commit/9dc848263fbf6509dd3e84a3a7963a897d14991b)) | ||
| * **api:** api update ([04c1163](https://github.com/autorenderhq/autorender-python/commit/04c116350cc7a2f5f288a8fd9febd020083cf536)) | ||
| * **api:** api update ([b4d6dbe](https://github.com/autorenderhq/autorender-python/commit/b4d6dbee14ac3e753968ce90388eaf01d2af4b94)) | ||
| * **api:** api update ([3932736](https://github.com/autorenderhq/autorender-python/commit/393273609afc67cc8b30d33bb27861edb1e20988)) | ||
| * **api:** api update ([58346bd](https://github.com/autorenderhq/autorender-python/commit/58346bdeba4b11a33fd1e63c69fceb432424bdf0)) | ||
| * **api:** api update ([7fdb60a](https://github.com/autorenderhq/autorender-python/commit/7fdb60a62af1ae9fd716c3a9939d2cc128bd4a85)) | ||
| * **api:** api update ([79c95b0](https://github.com/autorenderhq/autorender-python/commit/79c95b0a55d59e214f0b00936a5b517c0f66ca13)) | ||
| * **api:** api update ([b43e6a1](https://github.com/autorenderhq/autorender-python/commit/b43e6a1b4b157808d3ef2606552df4e68c1524e7)) | ||
| * **api:** api update ([658511c](https://github.com/autorenderhq/autorender-python/commit/658511ca294a346646139b0c4c5e0f4e151115e4)) | ||
| * initial stlc build ([0bdb709](https://github.com/autorenderhq/autorender-python/commit/0bdb709b1d8e670a795f867f71fab9c3ef6be539)) | ||
| * **internal/types:** support eagerly validating pydantic iterators ([477052f](https://github.com/autorenderhq/autorender-python/commit/477052fa9cd1ff89c96ee4b8febf010851c6501e)) | ||
| * support setting headers via env ([749df21](https://github.com/autorenderhq/autorender-python/commit/749df21f7ac657d44cb297707a5ec2506bcb0df9)) | ||
|
|
||
|
|
||
| ### Bug Fixes | ||
|
|
||
| * **client:** add missing f-string prefix in file type error message ([0f93e15](https://github.com/autorenderhq/autorender-python/commit/0f93e15723c120a2f409cf2884d085f7966d5d0c)) | ||
| * **examples:** use timestamp names and correct response shape in files.py ([b4d13a7](https://github.com/autorenderhq/autorender-python/commit/b4d13a7d72784c4448424db46495c985276773d3)) | ||
| * install rye for Python SDK bootstrap ([5f089bf](https://github.com/autorenderhq/autorender-python/commit/5f089bf37c183b4d41b1eb1787c5b7390d93b0f2)) | ||
| * **pagination:** resolve pyright incompatible override for has_next_page ([5cf6e56](https://github.com/autorenderhq/autorender-python/commit/5cf6e565ac0aeecdc5e59b887b1e008892eed1ce)) | ||
| * **python:** rename pagination field has_next_page -> has_next to fix pyright lint ([729d204](https://github.com/autorenderhq/autorender-python/commit/729d20471bdfe545acdea2e443cfb2b8436ba08a)) | ||
| * strip Content-Type header for body-less requests; add examples ([c3591d0](https://github.com/autorenderhq/autorender-python/commit/c3591d02910ded15e21a7ed7da402bf149f46857)) | ||
| * use correct field name format for multipart file arrays ([f968ef9](https://github.com/autorenderhq/autorender-python/commit/f968ef95330967c6b888ea3fc89c85f12ee926d1)) | ||
|
|
||
|
|
||
| ### Performance Improvements | ||
|
|
||
| * **client:** optimize file structure copying in multipart requests ([498d621](https://github.com/autorenderhq/autorender-python/commit/498d621cc46637650c03f1ed9d00749dbcab9c99)) | ||
|
|
||
|
|
||
| ### Chores | ||
|
|
||
| * **internal:** more robust bootstrap script ([798e8b7](https://github.com/autorenderhq/autorender-python/commit/798e8b79c22e0173d4f30a80924dcad627cc838f)) | ||
| * **internal:** reformat pyproject.toml ([fcc4169](https://github.com/autorenderhq/autorender-python/commit/fcc4169f137c6f4e6305bd0b8133658ad5337aa6)) | ||
| * remove examples from SDK (moved to stainless-examples runner) ([12a383e](https://github.com/autorenderhq/autorender-python/commit/12a383e16ab6e856905dd8ce8f3f666ff914c43c)) | ||
| * **tests:** bump steady to v0.22.1 ([30a0e81](https://github.com/autorenderhq/autorender-python/commit/30a0e8184adf8271f879cb9e5175ed52404a0043)) | ||
| * update SDK settings ([aead4ee](https://github.com/autorenderhq/autorender-python/commit/aead4ee8dd9504134612b1845cd18576b7c58848)) | ||
| * update stlc custom-code tracking files ([505f95e](https://github.com/autorenderhq/autorender-python/commit/505f95e9e6b66928d05ffa5b630102fdfe3b5e3e)) | ||
|
|
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Remove the duplicated 0.1.0 entry.
Lines 54-99 already add a linked 0.1.0 section, but Line 100 starts a second 0.1.0 block immediately after it. Publishing both makes the release history ambiguous.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@CHANGELOG.md` around lines 54 - 99, The CHANGELOG has a duplicated release
section for 0.1.0, which makes the release history ambiguous. Remove the extra
0.1.0 heading/block so only one release entry remains for that version, keeping
the linked compare header and the existing Features/Bug Fixes/Chores content
under the single 0.1.0 section.
Merged
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.
207ad4f Build SDK
Summary by CodeRabbit
New Features
Bug Fixes
Chores