release: 1.6.1 #1002
Merged
release: 1.6.1 #1002
Conversation
This file contains 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
The previous version of the README contained a code example with a missing comma, which could lead to syntax errors. This commit corrects that issue by adding the missing comma.
stainless-bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
ce5c027 to
3c8dd71
Compare
stainless-bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
eeef935 to
ceaf9a0
Compare
athyuttamre
approved these changes
Dec 22, 2023
stainless-bot
deleted the
release-please--branches--main--changes--next
branch
|
🤖 Release is at https://github.com/openai/openai-python/releases/tag/v1.6.1 🌻 |
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.6.1 (2023-12-22)
Full Changelog: v1.6.0...v1.6.1
Chores
This Pull Request has been generated automatically as part of Stainless's release process.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request (see details).
More technical details can be found at stainless-api/release-please.