release: 0.5.0#7
Merged
kriptoburak merged 14 commits intoJul 22, 2026
Merged
Conversation
Pin all GitHub Actions referenced in generated workflows (both first-party `actions/*` and third-party) to immutable commit SHAs. Updating pinned actions is now a deliberate codegen-side bump rather than implicit on every workflow run.
…t in workflow templates
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 21, 2026 07:21
381d6fa to
7101993
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
2 times, most recently
from
July 21, 2026 07:21
4d0d2b8 to
7ef51ef
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 22, 2026 15:46
7ef51ef to
dc6936c
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 22, 2026 15:53
dc6936c to
627fd66
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 22, 2026 16:13
627fd66 to
ca92bf0
Compare
Contributor
Author
|
🤖 Release is at https://github.com/Xquik-dev/x-twitter-scraper-php/releases/tag/v0.5.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
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.5.0 (2026-07-22)
Full Changelog: v0.4.5...v0.5.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
Note
Add idempotency key support and durable write-action lifecycle models across all write operations
$idempotencyKeyargument; it is forwarded as anIdempotency-KeyHTTP header and excluded from the request body.TweetNewResponse,LikeDeleteResponse,DmSendResponse) are expanded from minimal shapes into full durable write-action records with many required fields (id,account,billing,status,target, etc.) and a fixedobject = 'x_write_action'discriminator.Billing,NextAction,Request,Result,Target,Status,Action) to type the new lifecycle fields.createandreplymethods and params gain an optional$idempotencyKey; ticket responses gain a requiredattachmentslist and requiredpublicID.Errorgains optionalmessage,reason,retryAfter, andretryAfterMsfields.with()static constructors on response models must be updated to supply the new required parameters; previous zero-arg or minimal-arg usage is no longer valid.Macroscope summarized ca92bf0.