Skip to content

release: 5.18.1#53

Open
stainless-app[bot] wants to merge 2 commits into
mainfrom
release-please--branches--main--changes--next
Open

release: 5.18.1#53
stainless-app[bot] wants to merge 2 commits into
mainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app

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

Copy link
Copy Markdown
Contributor

Automated Release PR

5.18.1 (2026-07-23)

Full Changelog: v5.18.0...v5.18.1

Documentation

  • openapi: describe user topic-preference fields explicitly (#172) (7a0f629)

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

stainless-app Bot and others added 2 commits July 23, 2026 23:47
Add field descriptions to UsersTopicPreference and UsersTopicPreferenceUpdate
so the generated API reference documents them fully (topic_id, status,
default_status, has_custom_routing, custom_routing, topic_name), including the
REQUIRED-is-a-topic-default semantics and the custom_routing channel set. Wrap
the PreferenceStatus $ref fields in allOf so the description renders under
OpenAPI 3.0.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

0 participants