Fix: declare trust_probe capability to unbreak Inngest Cloud sync (v1.4.5)#11
Merged
Merged
Conversation
Inngest Cloud's /fn/register endpoint started returning 400 "Invalid response returned" on 2026-05-22 for SDKs that don't advertise the trust_probe capability. The TS SDK has always declared this; the .NET SDK was silently relying on legacy fallback behavior that has now been removed. - Out-of-band register payload now includes capabilities.trust_probe=v1 and in_band_sync=v1. - In-band sync inspection adds trust_probe=v1 alongside the existing in_band_sync=v1. - Authenticated GET introspection response includes the same capabilities block (mirrors the TS SDK). - Added regression test that captures the outbound /fn/register POST body and asserts capabilities are present. - Bumped version to 1.4.5. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
Inngest Cloud's `/fn/register` endpoint started returning `400 "Invalid response returned"` on 2026-05-22 for SDKs that don't advertise `capabilities.trust_probe = "v1"`. The TS SDK has always sent this; the .NET SDK was silently relying on legacy fallback behavior that Cloud has now removed. This broke every CoolFocus release pipeline run since 16:35 UTC — the sync step fails and cascades to skipping Linear/Sentry release tracking.
Changes
Test plan
🤖 Generated with Claude Code