Run details

GhostWorkspace

CI Pipeline Executions
- Current executionSucceeded
  feat/stripe-checkout-collection
- Runs and Agents
- Configuration
- Self-Healing CI
- Project Graph
- Resource Usage
- Analysis
- Conformance
Runs
- Current runSucceeded
- Tasks
- Resource Usage

Insights

Compare tasks
Analytics

Added Stripe checkout collection into member custom fields A tier could say what its checkout should collect and where each answer belongs, and nothing acted on it. This connects the two ends: the session Ghost creates now asks for what the tier configured, and the completed session's answers are written into the member's fields. What comes back is read as ports and values, so nothing outside the bindings knows a field key, and each value is written in its own transaction — atomic across the parts of an address, but no wider, because a postcode a processor formatted differently must not cost the phone number beside it. None of it may fail the webhook, which is busy creating the member and linking the subscription. The limits a checkout page enforces were measured against the live API rather than read from the reference, which disagreed with it in three of five probes. One of those measurements matters on its own: Stripe will not collect a tax number for a customer it may not rename, so a tier that asked for one could not be bought by a member who already had a Stripe customer. A site that has configured nothing sends a request identical to the one it sent before, and the whole path stays behind the members custom fields flag. ref https://linear.app/ghost/issue/BER-3872

nx run ghost:test:integration

Succeeded

4 CPU cores

read-write access token used

5d7c670030309

91%

Cache hits

21 of 23 tasks used cache.

Protect cache integrity with sandboxing

Get faster results

Learn how to enable distribution.

Atomizer enabled

22 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools