release: 7.24.0 - #150
Open
stainless-app[bot] wants to merge 3 commits into
Open
Conversation
…180) Follow-up to #179, rebased onto the Broadcasts merge (#170). Three changes to `specs/openapi.yml`: 1. **Reorders the sections** so the API reference reads in the same order as the Studio left nav — Content (Templates, Brands, Routing) → Orchestration (Journeys, Broadcasts) → Directory (Users, Tenants, Audiences, Lists) → Platform (Providers, Preferences) — with Send first and everything that has no nav home below. 2. **Declares the missing `Broadcasts` tag.** #170 added 11 Broadcasts operations but no entry in the top-level `tags:` array, so they were rendering as an undeclared group at the end of the sidebar, and the paths themselves sat inside the Templates section. They now have their own section, in the Studio nav's position right after Journeys. 3. **Renames `Profiles` → `User Profiles`**, matching the endpoints under it and the "user profile" language used everywhere else in the docs. Authentication moves off the top to the bottom: it is one endpoint that only client-side SDKs call, so it was crowding out Send. New order: Send · Templates · Brands · Routing Strategies · Journeys · Broadcasts · User Profiles · Tenants · Audiences · Lists · Providers · Preference Topics · User Preferences then, below the fold: Messages · Device Tokens · Tenant Memberships · Tenant Templates · Automations · Digests · Translations · Inbox · Track Events · Audit Events · Authentication Verified mechanical: parsing the spec before and after shows 85 paths and 147 operations in both, zero operation-body differences, and the only semantic changes are the `Profiles` → `User Profiles` tag on the 8 `/profiles/*` operations and the added `Broadcasts` tag declaration. `components:`, `servers:`, `info:`, and `security:` are unchanged, as are all 23 pre-existing tag descriptions. Every tag an operation carries is now declared, and every declared tag is used. No SDK surface is affected — Stainless resources come from `stainless.yml`, which this PR does not touch. Renaming the section changes its API reference slugs, so the docs side needs `/api-reference/profiles/*` → `/api-reference/user-profiles/*` redirects. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
Author
|
🧪 Testing To try out this version of the SDK: Expires at: Sat, 29 Aug 2026 17:25:10 GMT |
…19268) (#182)
Reverts the public documentation of DELETE /inbox/messages/{message_id} and
PUT /inbox/messages/{message_id}/restore (added in #175). The server-side delete
endpoint authenticates and returns 204, but the soft-delete is not reflected in
the inbox read path the SDK/clients use (deleted messages still appear in the
in-app inbox). Pulling the endpoints from the public API surface + SDK generation
until the read-path issue is resolved.
Removes:
- openapi.yml: both paths + the Inbox tag (only used by these two operations)
- stainless.yml: the inbox.messages resource (delete + restore)
Co-authored-by: Mike Miller <mike@courier.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
July 30, 2026 17:24
b056dc8 to
4c7b0e1
Compare
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
7.24.0 (2026-07-30)
Full Changelog: v7.23.0...v7.24.0
Features
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