Repository navigation
Conversation
This branch has not been deployed
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.
Synchronize the vendored public OpenAPI bundle and generated internal client with Hosting #3213 while preserving the existing OAuth provider facade for both older three-field and current five-field responses. The whole-spec refresh includes accumulated Sandbox, Connector and LavaFlow changes since SDK base
340c9a3eabb00b3bc74557aaa4114e967e0752c8: 468 files (+71,584 / -17,735), including the original 460-file synchronization and native compatibility/fixture corrections.The LavaFlow additions expose optional confirmed severity, a filtered recorded PR branch and the saved proposed patch title; they do not assert a verified or shipped fix. No public facade operation is added. The OAuth facade continues to return only the provider name and linkage timestamps. Its native boundary accepts responses predating the provider ID/login fields, retains malformed provider/date rejection, and validates timezone ranges before parsing. New regressions exercise the public facade through the real transport for legacy/current payloads, malformed or missing public fields, impossible dates/offsets, fractional timestamps and empty collections. All pre-sync assertions are preserved. The PR-introduced test that required an unused provider ID is corrected to reflect the existing public contract.
The valid domain-response fixture includes
redirect: null, matching the canonical required nullable field and actual nonredirecting server response; all TLS and legacy-routing assertions remain. The deliberately incomplete custom-transport model is constructed with a scoped test fixture mutation so the existing SDK validation is still exercised.Source: Hosting
134dfb1196d944b20d6fb9f0ddf4e9984af6287d(#3213), public bundled OpenAPI SHA-2568bc109d5034348f37d1ab4d5a968db51b376c85ebf8e6386ea49c4ddcc6b0f23. The generated tree and bundle are unchanged by the native repairs. This supersedes the older snapshot proposed by the untouched bot sync #2; its CI does not validate this branch.The canonical generator completed before the native repairs. Targeted formatting and independent source/security review passed for this repaired head; fresh native CI is pending. Generation freshness, dependency audit, lint, type, unit, package, mutation and Quality Gate checks remain required. Draft-skipped AI/security checks are not passes. Public documentation and shared behavioral acceptance are coordinated in Hosting #3213. Land the required SDK updates before Hosting. No package publication is included.