release: 0.106.0 - #677
Merged
stainless-bot merged 3 commits intoJun 27, 2025
Merged
Conversation
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--lithic
branch
2 times, most recently
from
June 26, 2025 14:09
63df279 to
dd2efdf
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--lithic
branch
from
June 27, 2025 00:24
81ecad6 to
0551c7c
Compare
stainless-bot
deleted the
release-please--branches--main--changes--next--components--lithic
branch
June 27, 2025 00:25
Contributor
Author
|
🤖 Release is at https://github.com/lithic-com/lithic-node/releases/tag/v0.106.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.106.0 (2025-06-27)
Full Changelog: v0.105.0...v0.106.0
Features
Bug Fixes
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