[DI-9563] Regenerate currents-examples for Currents v10#46
Draft
isturdy wants to merge 1 commit into
Draft
Conversation
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.
Summary
Regenerated Currents example payloads for v10 via
braze-currents-generate-examples(EMS wheel1.0.0.20260622133450+b02c117), as part of the v10 release (DI-9563).Meaningful changes:
users.UserDeleteRequest,users.UserOrphan,users.canvas.costep.Send,users.profile.Update(+canvas/costepCustom HTTP).users.messages.rcs.*(Abort, Click, Delivery, InboundReceive, Read, Rejection, Send).Note on the large Avro diff: ~83 other
.avrofiles show as changed but are byte-identical in length with unchanged JSON counterparts — this is Avro Object Container File random sync-marker churn (a fresh 16-byte marker per regeneration), not a semantic change. Committed as-is per the standard regenerate-everything flow.Companion PRs: currents-monorepo#368, deployments #26243/#26245, braze-docs #14271/#14272.
Follow the PR template checklist before merging.