Repository navigation
Conversation
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.
The HTTP transport currently treats only
200 OKas a successful delivery. Log endpoints that respond with another valid success status, such as202 Acceptedor204 No Content, therefore emit a misleading warning instead oflogged.This changes the status check to accept the full 2xx range while preserving the existing behavior for request errors and non-2xx responses. Regression coverage verifies that
204succeeds and that the300boundary still warns.The focused transport tests pass on Node.js 22, 24, and 26. The full unit and integration suites, TypeScript definitions, and ESLint also pass; ESLint reports the same 10 existing warnings.