tr
TryGhost
GitHub
Ghost
Workspace
GitHub
CI Pipeline Executions
Current execution
Succeeded
chore/stripe-fixture-collection-harness
Runs and Agents
Configuration
Self-Healing CI
Project Graph
Circular Dependencies
Enterprise
Resource Usage
Analysis
Conformance
Enterprise
Runs
Current run
Succeeded
Tasks
Resource Usage
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Fixed collection flags being read for truthiness Stripe's SDK form-encodes its request bodies, so a checkout that switched tax collection off arrives carrying the string "false" rather than the boolean. The fake server read that flag for truthiness, and a string is truthy whichever word it holds, so it refused a checkout that had asked for no tax number at all and named a requirement the request had already met. The existing tests missed it because they post JSON, where the flag is a real boolean, so the refusal only appeared under the encoding Ghost actually uses. The completion helper read the same flags the same way and would have let a test answer a question the page never rendered. ref https://linear.app/ghost/issue/BER-3872
nx run ghost-monorepo:lint:boundaries
⌘K
Succeeded
nx run ghost-monorepo:lint:boundaries
Click to copy
Linux
4 CPU cores
read-write
access token used
0b29b1d2
30304
GitHub
Ghost
Workspace