Skip to content

[CI bisect — do not review] INR schema change minus rail property - #650

Closed
ls-bolt[bot] wants to merge 1 commit into
mainfrom
07-06-ci-bisect-inr-csharp-no-rail
Closed

[CI bisect — do not review] INR schema change minus rail property#650
ls-bolt[bot] wants to merge 1 commit into
mainfrom
07-06-ci-bisect-inr-csharp-no-rail

Conversation

@ls-bolt

@ls-boltls-boltBot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Claim this PR — take ownership under your GitHub account

Throwaway diagnostic PR — do not review, will be closed shortly.

Bisecting the chronic Build SDKs for pull request / preview csharp failure on #646 (and #644): this branch carries the exact INR schema change from #646minus the new rail property, to determine whether rail is what breaks the Stainless csharp SDK build.

  • csharp preview goes green here → rail is the breaker
  • csharp preview stays red → the breakage is elsewhere in the schema change

Context: #646's preview failed twice with csharp: Your SDK build had a failure in the build CI job, which is a regression from the base state, as did auto-sync #644 which carries the same INR fields.

Slack thread: https://lightsparkgroup.slack.com/archives/D0BCM1RUHHU/p1783372549749679


🤖 bonded-titan(#1) | Feedback

@vercel

vercelBot commented Jul 6, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments
ProjectDeploymentActionsUpdated (UTC)
grid-flow-builderIgnoredIgnoredPreviewJul 6, 2026 10:16pm
grid-wallet-demoIgnoredIgnoredPreviewJul 6, 2026 10:16pm

Request Review

@ls-boltls-boltBot added the bolt label Jul 6, 2026
@github-actionsgithub-actionsBot added the breaking-change Introduces a breaking change to the OpenAPI spec label Jul 6, 2026
@akanterGraphite App

Copy link
Copy Markdown
Contributor

This stack of pull requests is managed by Graphite. Learn more about stacking.

@github-actions

github-actionsBot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

✱ Stainless preview builds for grid

This PR will update the grid SDKs with the following commit messages.

cli

chore(internal): regenerate SDK with no functional changes

csharp

feat(api): add account_number/bank_name/ifsc fields, neft/rtgs rails to inr external accounts

go

feat(api): add accountNumber/bankName/ifsc, make vpa optional in InrExternalAccountCreateInfo

kotlin

feat(api): add accountNumber/bankName/ifsc, NEFT/RTGS rails to INR accounts, make vpa optional

openapi

feat(api): add accountNumber/ifsc/bankName fields, NEFT/RTGS rails to InrAccountInfo

php

feat(api): add accountNumber/bankName/ifsc fields, NEFT/RTGS rails to INR accounts

python

feat(api): add account_number/bank_name/ifsc fields, make vpa optional in INR external account

ruby

feat(api): add account_number/bank_name/ifsc fields, NEFT/RTGS rails to INR accounts

typescript

feat(api): add NEFT/RTGS payment rails and account fields to INR external accounts

Edit this comment to update them. They will appear in their respective SDK's changelogs.

grid-openapistudio · code · diff

Your SDK build had at least one "warning" diagnostic, but this did not represent a regression.
generate ⚠️

grid-rubystudio · code · diff

Your SDK build had at least one "note" diagnostic, but this did not represent a regression.
generate ✅build ✅ (prev: build ⏭️) → lint ✅test ✅

grid-gostudio · code · diff

Your SDK build had at least one "note" diagnostic, but this did not represent a regression.
generate ✅build ✅ (prev: build ⏭️) → lint ❗test ❗

go get github.com/stainless-sdks/grid-go@d6d7c5575ac765d896370605b50fcf2161c79c3b
grid-kotlinstudio · code · diff

Your SDK build had at least one "warning" diagnostic, but this did not represent a regression.
generate ⚠️build ✅ (prev: build ⏭️) → lint ✅ (prev: lint ⏭️) → test ❗

⚠️grid-typescriptstudio · code · diff

Your SDK build had a failure in the lint CI job, which is a regression from the base state.
generate ✅build ✅ (prev: build ⏭️) → lint ❗ (prev: lint ⏭️) → test ✅

npm install https://pkg.stainless.com/s/grid-typescript/14610bb8c5a59a7526889f95f460bd8a1040e69d/dist.tar.gz
⚠️grid-pythonstudio · code · diff

Your SDK build had a failure in the lint CI job, which is a regression from the base state.
generate ✅build ✅ (prev: build ⏭️) → lint ❗ (prev: lint ⏭️) → test ❗

pip install https://pkg.stainless.com/s/grid-python/aebad761299d5cbc3d99cc5e33489187dcf5417b/grid-0.0.1-py3-none-any.whl
⚠️grid-csharpstudio · code · diff

Your SDK build had a failure in the build CI job, which is a regression from the base state.
generate ⚠️build ❗ (prev: build ⏭️) → lint ✅ (prev: lint ⏭️) → test ❗

grid-phpstudio · code · diff

Your SDK build had at least one "note" diagnostic, but this did not represent a regression.
generate ✅lint ✅test ✅

grid-clistudio · code · diff

Your SDK build had at least one "warning" diagnostic, but this did not represent a regression.
generate ⚠️build ❗lint ❗test ❗


This comment is auto-generated by GitHub Actions and is automatically kept up to date as you push.
If you push custom code to the preview branch, re-run this workflow to update the comment.
Last updated: 2026-07-06 22:20:45 UTC

@ls-bolt
ls-boltBotforce-pushed the 07-06-ci-bisect-inr-csharp-no-rail branch from 13aa9e8 to 848999aCompareJuly 6, 2026 22:02
@ls-bolt

ls-boltBot commented Jul 6, 2026

Copy link
Copy Markdown
ContributorAuthor

Round 1 result: csharp still failed with the full change minus railrail is not the breaker.

Round 2 (this push): branch now carries only the paymentRails enum addition (NEFT/RTGS) on InrAccountInfo — no new properties, vpa still required.


🤖 bonded-titan(#1) | Feedback

@github-actionsgithub-actionsBot removed the breaking-change Introduces a breaking change to the OpenAPI spec label Jul 6, 2026
@ls-bolt
ls-boltBotforce-pushed the 07-06-ci-bisect-inr-csharp-no-rail branch from 848999a to 912ad46CompareJuly 6, 2026 22:08
@ls-bolt

ls-boltBot commented Jul 6, 2026

Copy link
Copy Markdown
ContributorAuthor

Round 2 result: csharp failed on the enum-only diff (+NEFT/+RTGS, 2 lines) — a shape that already exists on EUR/DKK (SEPA, SEPA_INSTANT) and builds fine on main. The INR content is looking innocent.

Round 3 (this push): zero schema changes — a one-word edit to info.description ("full" → "complete"). If csharp still fails, ANY freshly-generated csharp build is currently broken in Stainless, and every spec-touching grid-api PR will go red regardless of content.


🤖 bonded-titan(#1) | Feedback

…iption), no structural changes (do not review)
@ls-bolt
ls-boltBotforce-pushed the 07-06-ci-bisect-inr-csharp-no-rail branch from 912ad46 to b1f940cCompareJuly 6, 2026 22:16
@ls-bolt

ls-boltBot commented Jul 6, 2026

Copy link
Copy Markdown
ContributorAuthor

Round 3 result: csharp passed on the info.description one-word edit — but that edit likely produces zero delta in generated csharp code, so Stainless may have reused a cached build. Not yet conclusive.

Round 4 (this push): a field-description-only change (GTQ bankName description) — semantically trivial but lands in generated doc comments, forcing fresh csharp codegen + CI.


🤖 bonded-titan(#1) | Feedback

@ls-bolt

ls-boltBot commented Jul 6, 2026

Copy link
Copy Markdown
ContributorAuthor

Round 4 result: csharp failed on a description-only change (GTQ bankName doc string). Conclusion proven:

The Stainless csharp target fails its build CI for ANY freshly-generated code right now, regardless of content. Diffs that don't change generated csharp (docs-only PRs, info.description tweaks) pass because Stainless reuses the cached build; anything that regenerates csharp code fails. The breakage window opened between Jul 3 09:10 UTC (#642, last code-changing pass) and Jul 6 18:34 UTC (#644, first of the current failures).

#646 is exonerated — its content is fine (all real spec gates green). The csharp target is unpublished (production_repo: null, nuget: false), so this check has no shipping impact. The actual error needs someone with Stainless Studio access (org lightspark, project grid) or Stainless support.

Closing this diagnostic PR.


🤖 bonded-titan(#1) | Feedback

@ls-boltls-boltBot closed this Jul 6, 2026
@ls-bolt
ls-boltBot deleted the 07-06-ci-bisect-inr-csharp-no-rail branch July 6, 2026 22:21
benwgold added a commit that referenced this pull request Jul 8, 2026
…#671)
## Summary
Removes the csharp target from `.stainless/stainless.yml` so the `Build
SDKs for pull request / preview` check stops failing on every
spec-changing PR.
**Why every spec PR is red**: Stainless's csharp build CI is broken
upstream for ANY freshly generated code (content-independent, proven by
bisect on #650, breakage window ~Jul 3). The preview check gates on a
per-language head-vs-base regression, and with csharp in main's config
the base build resolves to a cached pre-breakage csharp *success* — so
every fresh head failure counts as a regression → red.
**Why this fixes it**: with csharp out of the config on main, base
builds have no cached csharp success to regress from — matching outcomes
on base and head → "not a regression" → green. Proven end-to-end by
probe #659: the exact previously-failing change class (doc-comment-only
codegen delta) ran against a csharp-free base and `preview` **passed**.
Full mechanics: [investigation
writeup](#657 (comment)).
**No shipping impact**: the csharp target is unpublished
(`production_repo: null`, `publish.nuget: false`). Re-add the block when
Stainless fixes their csharp build CI upstream.
## Sequencing (for #657 and other open spec PRs)
1. Merge this PR — **its own `preview` will be red** (its base is
current main); merge through it (precedent: #633, #637).
2. Merge/rebase main into open spec PRs (e.g. #657) — their next
`preview` run goes green.
## Verification
- `make lint` passes; the file matches the exact removal previously
validated on the #657 branch (commit 069ad9a) and by probe #659.
---
🤖
[thundering-graviton-3](https://zeus.dev.dev.sparkinfra.net/#/arc?id=thundering-graviton)[(#3)](https://zeus.dev.dev.sparkinfra.net/#/instance?id=thundering-graviton-3)
| [Feedback](https://zeus.dev.dev.sparkinfra.net/feedback)
Original PR: #663
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@akanter@mohamedwane