Skip to content

release: 0.5.0#7

Merged
kriptoburak merged 14 commits into
mainfrom
release-please--branches--main--changes--next
Jul 22, 2026
Merged

release: 0.5.0#7
kriptoburak merged 14 commits into
mainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app

@stainless-app stainless-app Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Automated Release PR

0.5.0 (2026-07-22)

Full Changelog: v0.4.5...v0.5.0

Features

  • api: propagate durable write actions (afddb86)
  • api: propagate production write-action contract (487bbf4)
  • stlc: configurable CI runner and private-production-repo support in workflow templates (88e3023)
  • support setting headers via env (e4c47e9)

Bug Fixes

  • guzzle requires special handling to enable streaming (519f14f)

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

  • All write operation methods (tweets, likes, retweets, follows, DMs, media, profile, communities) now require a string $idempotencyKey argument; it is forwarded as an Idempotency-Key HTTP header and excluded from the request body.
  • All write-operation response models (e.g. 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 fixed object = 'x_write_action' discriminator.
  • Dozens of new nested value-object classes and enums are introduced per response namespace (e.g. Billing, NextAction, Request, Result, Target, Status, Action) to type the new lifecycle fields.
  • Support ticket create and reply methods and params gain an optional $idempotencyKey; ticket responses gain a required attachments list and required publicID.
  • Error gains optional message, reason, retryAfter, and retryAfterMs fields.
  • Risk: All callers of write-operation service methods and 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.

@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 381d6fa to 7101993 Compare July 21, 2026 07:21
@stainless-app stainless-app Bot changed the title release: 0.4.1 release: 0.5.0 Jul 21, 2026
@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next branch 2 times, most recently from 4d0d2b8 to 7ef51ef Compare July 21, 2026 07:21
@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 7ef51ef to dc6936c Compare July 22, 2026 15:46
@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from dc6936c to 627fd66 Compare July 22, 2026 15:53
@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 627fd66 to ca92bf0 Compare July 22, 2026 16:13
@kriptoburak
kriptoburak merged commit 29270f7 into main Jul 22, 2026
11 checks passed
@stainless-app

stainless-app Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant