Repository navigation
Update generated code for beta - #2018
Merged
Merged
Conversation
stripe-openapi
Bot
requested review from
mnorth-stripe
and removed request for
a team
November 2, 2026 18:41
stripe-openapi
Bot
force-pushed
the
latest-codegen-beta
branch
from
November 2, 2026 18:41
a47cf73 to
f36585d
Compare
stripe-openapi
Bot
force-pushed
the
latest-codegen-beta
branch
24 times, most recently
from
November 4, 2026 22:21
c8a80cc to
b0e37e1
Compare
stripe-openapi
Bot
force-pushed
the
latest-codegen-beta
branch
15 times, most recently
from
November 11, 2026 17:08
7c559b3 to
1f3f94c
Compare
Point the major changefile's migration guide link at the published wiki page and rebuild CHANGELOG.md. The previous link pointed at a branch or repo path that can move or be deleted. Committed-By-Agent: claude Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
stripe-openapi
Bot
force-pushed
the
latest-codegen-beta
branch
2 times, most recently
from
November 12, 2026 18:40
9ea19e8 to
5f0a6b1
Compare
…es (#2026) * Persist stripe_context in OPTS_PERSISTABLE stripe_context identifies which account/workspace a resource belongs to -- the same reason stripe_account already persists -- but it was excluded from OPTS_PERSISTABLE alongside idempotency_key, which persists for an unrelated reason (each request needs its own fresh key). No documented reason for the exclusion could be found (git history traces to a single squashed merge, stripe-ruby-next shares the same squashed history, no PR comments). Without this, an object fetched through a context-scoped client loses that context the moment it's no longer backed by the original scoped requestor -- concretely, across a Marshal round-trip (e.g. a Rails cache), since @opts is the only part of a StripeObject that survives serialization. A later mutation on the restored object then authenticates under whatever account happens to be ambient in the loading process instead of the one it was actually fetched under. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Committed-By-Agent: claude * Drop stripe_account whenever stripe_context is present Stripe-Account and Stripe-Context are mutually exclusive on the wire (sending both is rejected). merge_config_and_opts computed them independently, so a stale stripe_account could ride along with a correct stripe_context -- the exact shape of bug this ticket is about, just reachable through more than one path. Enforcing this in merge_config_and_opts covers every caller uniformly (StripeObject#_request, request_stripe_object's execute_request_initialize_from, and EventBase#_request all funnel through it before a request is dispatched or an object's opts are persisted), so EventBase no longer needs its own dedicated scoped_requestor to force stripe_account: nil -- that was working around the lack of this rule in the shared merge logic. It still needs to supply stripe_context from the event's own `context` field, since nothing generic knows to do that. Two existing tests asserted both headers being sent together as correct behavior; updated them to match the real wire contract. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Committed-By-Agent: claude * Bind resource scopes during construction and Marshal restoration Committed-By-Agent: codex Co-authored-by: codex <noreply@openai.com> * Require explicit requestors in resource request helpers Committed-By-Agent: codex Co-authored-by: codex <noreply@openai.com> * Use the bound requestor directly for legacy save Committed-By-Agent: codex Co-authored-by: codex <noreply@openai.com> * Resolve requestors at construction boundaries Committed-By-Agent: codex Co-authored-by: codex <noreply@openai.com> * Align event scope fixtures with the API contract Committed-By-Agent: codex Co-authored-by: codex <noreply@openai.com> * Retain only the original requestor response key Committed-By-Agent: codex Co-authored-by: codex <noreply@openai.com> * Track last responses with a stack of request blocks Committed-By-Agent: codex Co-authored-by: codex <noreply@openai.com> --------- Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com> Co-authored-by: codex <noreply@openai.com>
stripe-openapi
Bot
force-pushed
the
latest-codegen-beta
branch
4 times, most recently
from
November 16, 2026 18:38
8590fef to
4ca9260
Compare
…2036) * Keep API keys out of YAML dumps of clients and event notifications EventNotification holds an internal StripeClient so fetch_event and fetch_related_object can make requests, and neither it nor the client's configuration had a YAML hook. Psych therefore dumped every instance variable, writing the API key (and any proxy credentials) into the YAML, e.g. when a notification is passed as a Delayed::Job argument. EventNotification#encode_with now omits the client. A restored notification keeps its fields, and requests through it raise an AuthenticationError pointing at parse_event_notification; YAML round trips already couldn't make requests. StripeConfiguration#encode_with omits the API key and proxy, which also covers StripeClient and APIRequestor dumps. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Committed-By-Agent: claude * Omit the configuration from requestor YAML instead of redacting the configuration A standalone StripeConfiguration YAML round trip restores a working configuration today, so stripping the API key there would change behavior for anyone relying on it. Requestor and client round trips already can't make requests, so omitting the configuration from APIRequestor's YAML keeps keys out of client and notification dumps without changing anything that currently works. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Committed-By-Agent: claude --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
stripe-openapi
Bot
force-pushed
the
latest-codegen-beta
branch
4 times, most recently
from
November 16, 2026 21:47
f2b10f8 to
45d5bad
Compare
…aa658fd9635eaf0107d13e3441
jar-stripe
approved these changes
Nov 19, 2026
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.
Codegen for openapi v2602 and v2 openapi f3581f76eec818aa658fd9635eaf0107d13e3441.
Changelog
V2::Billing::Cadencecreateandrefilltest helper methods on resourceCapital::FinancingOffercancel,create,list,retrieve, andupdatemethods on resourceV2::Billing::Cadenceexport_tax_transactions,product_tax_code_selector, andtax_threshold_monitoringonAccountSession::ComponentcustomonCouponCreateParamsandCoupontypeonCouponCreateParamsandCustomerCustomerBalanceTransactionCreateParamsapplied_to_invoiceonCustomerCustomerBalanceTransactionCreateParamscustomer_balanceonInvoiceandQuotePreviewInvoicePaymentIntent::NextAction::VerifyWithMicrodeposit.arrival_dateandSetupIntent::NextAction::VerifyWithMicrodeposit.arrival_datefromDateTimetonullable(DateTime)connect,data_export,event_destination,radar, anduser_accessonV2::Iam::ActivityLog::Detailapple_payonV2::MoneyManagement::OutboundSetupIntentCreateParams::PayoutMethodDatumandV2::MoneyManagement::PayoutMethodnetworkandoriginating_bank_accountonV2::MoneyManagement::ReceivedDebit::BankTransfercreatedonV2::MoneyManagement::ReceivedDebitListParamslogs_fromonV2::Iam::ActivityLogListParamsseverityonEventsV2CoreHealthEventGenerationFailureResolvedEvent