release: 1.100.0 #2562
Merged
release: 1.100.0 #2562
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
![stainless-app[bot]](https://avatars.githubusercontent.com/in/378072?s=60&v=4){kind=small}
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
1d86509 to
1ee5648
Compare
|
cool |
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
1ee5648 to
19e8009
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
19e8009 to
96aa605
Compare
kwhinnery-openai
approved these changes
Aug 18, 2025
stainless-app
bot
deleted the
release-please--branches--main--changes--next
branch
|
🤖 Release is at https://github.com/openai/openai-python/releases/tag/v1.100.0 🌻 |
| from .tool_choice_function import ToolChoiceFunction | ||
| from ..shared.responses_model import ResponsesModel | ||
| from .response_format_text_config import ResponseFormatTextConfig |
There was a problem hiding this comment.
Hello!,
I wanted to point out that changing ResponseTextConfig object name to ResponseFormatTextConfig breaks imports on several libs dependent on Openai's, including LiteLLM (also used as base for several other libs like dspy).
Shouldn't the approach here be to keep both object names, and deprecating the old one? Issuing a warning to help other developers prepare for future changes, or ensuring correct version freezes on their dependencies?
Also, making this change on a minor version (1.99 -> 1.100) in a way breaks backwards compatibility, which is assumed for semantic versioning.
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
1.100.0 (2025-08-18)
Full Changelog: v1.99.9...v1.100.0
Features
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