chore(targeting-client): regen for campaign:discover + entity_ui:status#414
Merged
praneetrohida merged 1 commit intoJul 15, 2026
Merged
Conversation
Regenerate @epilot/targeting-client from the current prod Targeting spec,
adding the Entity-UI Next Best Action operations the widgets MFE needs:
- discoverCampaigns (POST /v1/campaign:discover)
- updateRecipientEntityUiStatus (PATCH .../recipient/{id}/entity_ui:status)
Merging the openapi.json change triggers the @epilot/sdk auto-release, so
@epilot/sdk/targeting will expose these ops. Supersedes SIG-1276.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: Claude <noreply@anthropic.com>
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
2 participants
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.
Summary
Regenerates
@epilot/targeting-clientfrom the current prod Targeting API spec (https://docs.api.epilot.io/targeting.yaml), adding the two Entity-UI Next Best Action operations the widgets MFE needs to migrate off hand-rolledfetch:discoverCampaigns—POST /v1/campaign:discoverupdateRecipientEntityUiStatus—PATCH /v1/campaign/{campaign_id}/recipient/{recipient_id}/entity_ui:statusBoth endpoints are already live in prod (the spec at
docs.api.epilot.io/targeting.yamladvertises them, and the NBA widget already calls them via rawfetch).Changed files are the standard client-regen artifacts only (
src/openapi.json,src/openapi-runtime.json,src/openapi.d.ts) plus a patch version bump — perCONTRIBUTING.md"Updating clients". The@epilot/sdkpackage itself is not committed here: the CI auto-release regenerates and publishes@epilot/sdkwhen aclients/*/openapi.jsonchange lands onmain.Context
@epilot/sdkin the widgets MFE).ellebrink/feat-nba-discovery-endpointbranch is no longer needed and will be deleted.Test plan
npm run openapi(pulled prod spec — both ops present)npm run typegen && npm run buildsucceedpnpm generate-sdkconfirms@epilot/sdk/targetingexposesdiscoverCampaigns+updateRecipientEntityUiStatus@epilot/sdkauto-release publishes new version🤖 Generated with Claude Code