Skip to content

Merge to beta - #1988

Merged
zacchua-stripe merged 11 commits into
betafrom
zacchua/merge-python-beta
Nov 13, 2026
Merged

zacchua-stripe merged 11 commits into
betafrom
zacchua/merge-python-beta

Conversation

@zacchua-stripe

Copy link
Copy Markdown
Contributor

Why?

What?

See Also

Configuration

  • skip-changefile: This PR is not a user-facing change, so there's no changefile.

zacchua-stripe and others added 11 commits November 5, 2026 14:50
Move the static checks, build, and test steps into composite actions used by both CI and a new Canary CI workflow. Canary CI runs on pushes to the canary-ga, canary-beta, and canary-private-preview branches, points stripe-mock at the matching canary specs and fixtures, and has no publish job. CI job names are unchanged, so required status checks still match.


Committed-By-Agent: claude

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…bjects (#1968)

* Fix stale Stripe-Account header on directly-retrieved Event related objects

A directly-retrieved v2 Event keeps the requestor of whatever account
fetched it, so Event.fetch_related_object() could send a stale
Stripe-Account header alongside the event's own Stripe-Context.
EventNotification already avoids this in its own construction via
StripeClient.with_stripe_context; give Event the same treatment where
it's deserialized in _convert_to_stripe_object.

Fixes RUN_DEVSDK-3694.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Committed-By-Agent: claude

* Update requestor context handling in _util.py

Refactor handling of requestor context for v2 events.

---------

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
PycurlClient built the HTTPHEADER list via raw "%s: %s" string
interpolation with no validation, so a header value containing CR or
LF could inject an additional header line (e.g. via Stripe-Request-
Trigger, built from an unverified webhook event id). Other HTTP client
backends in this file are already protected by their own underlying
library (stdlib http.client, h11, aiohttp); pycurl has no such check
built in, so it needs one here.


Committed-By-Agent: claude

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
…s. (#1958)

The stripe-signature header may now include additional metadata about
the event destination and the event being sent. These can help narrow
down the reason why signature verification failed.

No changes are made to the verification process; this just updates how
error messages are generated, if the metadata is present in the header.
* Remove update-certs task from justfile

Removed the update-certs task from the justfile.

* Remove CA certificates update instructions from README

Removed instructions for updating bundled CA certificates.
…g 🪿✨ (#1959)

* [🪿] Omit API keys from StripeObject pickles

Prevent credentials from leaking into pickle-backed caches and queues.
Add graph-wide set_api_key() binding so consumers can supply their own
credentials while preserving routing and destination-global fallback.

Include regression tests and v16 migration guidance. Existing stored
pickles remain sensitive and are not sanitized by this change.

Committed-By-Agent: goose
Orbit-Session-Id: 6c16ab70-1263-4d0e-a050-72c9b9f30280

* [🪿] try to deslop

Consolidate overlapping pickle round-trip and credential-rebinding tests to remove duplicate setup and serialization. Retain coverage for supported pickle protocols, destination-global fallback, nested rebinding, routing preservation, and credential-free re-pickling without changing implementation behavior.

Verified 172 targeted tests pass, along with formatting, linting, and git diff whitespace checks.

Committed-By-Agent: goose
Orbit-Session-Id: 6c16ab70-1263-4d0e-a050-72c9b9f30280

* [🪿] Align pickle credential migration with v17

Document global fallback and explicit recursive key rebinding. Strengthen
nested requestor preservation coverage and remove task-specific README edits.

Committed-By-Agent: goose
Orbit-Session-Id: 6c16ab70-1263-4d0e-a050-72c9b9f30280

* [🪿] try to deslop

Remove redundant nested-resource serialization and assertions already covered by payload equality and credential-absence checks on re-pickled bytes. Recursive rebinding, cycle handling, routing preservation, standalone metadata serialization, and request-boundary coverage remain intact.

Validated with 101 passing StripeObject tests, formatting, linting, and git diff --check.

Committed-By-Agent: goose
Orbit-Session-Id: 6c16ab70-1263-4d0e-a050-72c9b9f30280

* [🪿] Update PyPI publishing action to v1.14.3

Fix the workflow security check failing on GHSA-5xjx-3w67-w9x9.
Pin the patched release to its verified commit SHA.

https: //github.com/advisories/GHSA-5xjx-3w67-w9x9
Committed-By-Agent: goose
Orbit-Session-Id: 6c16ab70-1263-4d0e-a050-72c9b9f30280

* [🪿] Revert unrelated PyPI publishing action upgrade

Keep CI configuration unchanged to scope this branch to pickle credentials.

Committed-By-Agent: goose
Orbit-Session-Id: 6c16ab70-1263-4d0e-a050-72c9b9f30280

* [🪿] Update pickle credential changefile wording and filename

* [🪿] Simplify v17 pickle migration guidance

Use concise examples to explain explicit API-key rebinding and global fallback.
Clarify that rebinding preserves current requestor configuration, not the
producer's custom HTTP client.

* [🪿] Replace set_api_key with per-call API keys on instance methods

Remove StripeObject.set_api_key() and instead accept an api_key on the
instance methods that previously could not take one: refresh(),
refresh_async(), save(), and auto_paging_iter() on ListObject,
SearchResultObject, and their V2 equivalents. delete() and generated
instance methods already accept per-call request options.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Committed-By-Agent: claude

* [🪿] Trim pickle credential changefile wording

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Committed-By-Agent: claude

* Require explicit API key reattachment after unpickling

Committed-By-Agent: codex
Co-authored-by: codex <noreply@openai.com>

* Keep serialized placeholders in requestors and guard requests centrally

Committed-By-Agent: codex
Co-authored-by: codex <noreply@openai.com>

* Clarify API key reattachment wording in changefile

Committed-By-Agent: codex
Co-authored-by: codex <noreply@openai.com>

* Clarify API key reattachment migration guidance

Committed-By-Agent: codex
Co-authored-by: codex <noreply@openai.com>

* Address serialization documentation review feedback

Committed-By-Agent: codex
Co-authored-by: codex <noreply@openai.com>

* Make migration guide before/after examples equivalent

Keep the Before and After snippets identical apart from the reattach step,
and move the list/event usage into a separate example.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Committed-By-Agent: claude

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: codex <noreply@openai.com>
PycurlClient created one pycurl.Curl handle in its constructor and
reconfigured it for every request with no synchronization. When one
client was shared across threads, concurrent requests could overwrite
each other's URL, body, and headers, sending one request with another
request's API key and Stripe-Account.

Each thread now lazily creates its own handle in the client's existing
thread-local storage, so connections are still reused within a thread.
close() closes the current thread's handle.

Closes RUN_DEVSDK-3704


Committed-By-Agent: claude

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts:
#	.hark/releases.json
#	CHANGELOG.md
#	VERSION
#	pyproject.toml
#	stripe/_version.py
@zacchua-stripe
zacchua-stripe requested a review from a team as a code owner November 12, 2026 18:09
@zacchua-stripe
zacchua-stripe requested review from ramya-stripe and removed request for a team November 12, 2026 18:09
@zacchua-stripe
zacchua-stripe merged commit 9598c0f into beta Nov 13, 2026
21 checks passed
@zacchua-stripe
zacchua-stripe deleted the zacchua/merge-python-beta branch November 13, 2026 20:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants