release: 0.79.0 #504
Merged
release: 0.79.0 #504
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
chore(internal): improve sync service tests docs: readme parameter tweaks
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
2 times, most recently
from
fd10019 to
bab2b10
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
7a23d20 to
0182c4b
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
d5427fe to
ecf5050
Compare
Note that previously the `timeout(Duration)` method on the client and `RequestOptions` corresponded to connect, read, write, and request timeout. Now it only corresponds to the request timeout. Use the new `timeout(Timeout)` method to configure other timeout values granularly.
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
62f72a7 to
17f97db
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
5d0f931 to
17f97db
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
483f9f3 to
112fd32
Compare
chore(internal): move `HttpRequestBodies` file chore(internal): extract function for checking for lists in json fields # Migration 1. Builder methods that used to take `contentType` and `filename` as positional parameters after the main argument now no longer do. To set a custom `contentType` or `filename`, pass `MultipartField`, which can be constructed via `MultipartField.builder()`. 2. It's unlikely you were referencing it, but `MultipartFormValue` is now called `MultipartField` if you were.
… Holder endpoint (#514) - Changes to Update Account Holder Endpoint: https://docs.lithic.com/changelog/editing-account-holder-updates - New Settlement API Endpoints: https://docs.lithic.com/changelog/february-25-2025
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
5 times, most recently
from
88136bd to
fa8d950
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
b5bf73b to
de0b778
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
bd4fa4c to
9242559
Compare
stainless-app
bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
ec4bebc to
a726256
Compare
Contributor
Author
|
🤖 Release is at https://github.com/lithic-com/lithic-java/releases/tag/v0.79.0 🌻 |
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.79.0 (2025-03-06)
Full Changelog: v0.78.0...v0.79.0
⚠ BREAKING CHANGES
Features
InputStreamandPathfor file params (#519) (de0b778)Bug Fixes
Chores
Optional, not nullable, fromClientOptions(#517) (fa8d950)ErrorHandlingTest(#509) (ecf5050)ServiceParamsTest(#507) (bab2b10)Documentation
builderjavadoc (#516) (7279322)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