release: 0.23.0#235
Merged
stainless-bot merged 5 commits intomainfrom Nov 8, 2023
Merged
Conversation
stainless-bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
8201678 to
ac40586
Compare
stainless-bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
f31146f to
d747b8c
Compare
stainless-bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
4e66e93 to
3e4efea
Compare
stainless-bot
deleted the
release-please--branches--main--changes--next
branch
Collaborator
Author
|
🤖 Release is at https://github.com/lithic-com/lithic-python/releases/tag/v0.23.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.23.0 (2023-11-08)
Full Changelog: v0.22.2...v0.23.0
Features
Bug Fixes
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.