release: 7.19.2#249
Merged
mikemilla merged 3 commits intoJul 10, 2026
Merged
Conversation
* docs(openapi): use canonical type-id prefixes in id examples
Align example ids with the backend's type-id prefixes (backend staging,
lib/courier-ids ID_PREFIXES): nt=notification, rs=routing-strategy,
pc=provider-config, ps=preference-section, pt=preference-topic.
- providers: prov_ -> pc_ (wrong prefix corrected)
- preference sections: PS5QM... -> ps_<typeid>
- preference topics: raw ULIDs and "marketing" -> distinct pt_<typeid>
(the valid vs not-found example ids are kept distinct)
- notifications / routing: normalize the fake-short nt_01abc123 /
rs_01abc123 to valid 26-char typeids
All new values are format-valid typeids (prefix_ + 26-char base32),
generated with typeid-js. Scope is "typed fields only": path
{id}/{section_id}/{topic_id} params and clearly-named id fields for the
5 entities that have prefixes. The shared generic placeholder abc-123
(used across many unrelated entities) and the already-correct, readable
elem_* element ids are left as-is. Examples-only; no schema/contract change.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* test(e2e): make the journeys invoke test self-contained
The "lists journeys and invokes the first template" test invoked
list.templates[0], which is flaky against the shared live workspace: when
no journey happens to exist there the list is empty and the test fails on
`expect(firstId).toBeDefined()` (data drift, not a regression). Every other
test in this file creates its own journey; make this one do the same —
create + publish a minimal api-invoke journey, then invoke it by id. `list`
is still covered by the "lists journeys" test above.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
Author
|
🧪 Testing To try out this version of the SDK: Expires at: Sun, 09 Aug 2026 00:05:26 GMT |
* docs(openapi): canonical type-id prefixes in remaining id examples Follow-up to #160, which normalized nt/rs/pc/ps/pt id examples but left a few prefixed-entity ids using placeholder/short values. Align these with the backend's canonical type-id prefixes (staging lib/courier-ids ID_PREFIXES): - routing: strategy_id "rs_123" -> valid rs_ typeid (matches the rs_ example used elsewhere in the spec) - error messages: "Notification template nt_nonexistent not found" and "Routing strategy rs_nonexistent not found" -> valid-format not-found typeids (distinct from the "exists" example ids, per #160's valid-vs-not-found convention) - error message: "Version not found for template nt_123" -> canonical nt_ typeid (the template exists; only the version is missing) All values are format-valid typeids (prefix_ + 26-char base32), generated with typeid-js. Readable elem_* element ids are left as-is (element ids are idiomatically human-readable in this spec). Examples-only; no schema/contract change. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * docs(openapi): use canonical jry_ / nt_ ids in journey examples Latest backend staging lib/courier-ids ID_PREFIXES added a JOURNEY: "jry" prefix (journey create always generates a jry_ typeid). The journeys example ids were still placeholders — align them: - journey ids (list items, create/get/replace/publish responses): abc-123 / abc-123-def-456 / xyz-789-ghi-012 -> jry_ typeids - journey-scoped notification templates (POST /journeys/{templateId}/templates results): tmpl-1 / tmpl-2 -> nt_ typeids Left as-is: journey node ids (trigger-1, send-1) are user-authored readable ids; run_id/runId are X-Ray-style run identifiers, not typeids; brand/tenant ids stay readable placeholders (both accept customer-supplied ids, matching #160). /automations examples are untouched (automation template ids are composite tenant/env-scoped, not a bare jry_). All new values are format-valid typeids (prefix_ + 26-char base32), generated with typeid-js. Examples-only; no schema/contract change. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * docs: canonical brand/notification/routing ids + release-shepherd note Complete the type-id sweep so every prefixed-entity example uses a canonical typeid, and document the release-shepherd skill. openapi.yml (examples-only, no schema/contract change): - brand ids -> bnd_ (Brand, BrandsResponse, Tenant/TenantListResponse brand_id, RoutingStrategyGetResponse brand_id, and brand.id in notification responses): brand now has a canonical bnd prefix on staging, so the placeholder ULID / brand_abc values are replaced - NotificationListResponse item id: abc-123 -> nt_ (was missed) - RoutingStrategyGetResponse id: abc-123 -> rs_ (was missed) - BulkGetJobUsersResponse templateId -> nt_ Left readable/untouched (not backend-generated typeids): tenant/workspace ids (customer-supplied, wrk_ is only the generated fallback), tag ids, submission-check ids, audit-event ids, and /automations template ids (composite tenant/env-scoped, not a bare jry_). README: add a note pointing to the courier-release-shepherd skill for driving the docs sync + SDK release PRs after a merge. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--courier
branch
from
842015f to
a941d84
Compare
Contributor
Author
|
🤖 Release is at https://github.com/trycourier/courier-node/releases/tag/v7.19.2 🌻 |
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
7.19.2 (2026-07-10)
Full Changelog: v7.19.1...v7.19.2
Documentation
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