Repository navigation
Fix HTTP error handling and prepare 1.0.1 - #1
Merged
Merged
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.
Interrupted HTTP error bodies previously became NetworkError with no status. Malformed entries in a server message array could also hide a 429 response and its Retry-After header. Preserve the HTTP error class, status, and headers, retain body failures as cause, and ignore non-string message entries. Explicit cancellation and client timeouts keep their existing behavior.
Prepare version 1.0.1 and use the configured npm trusted publisher without the obsolete NPM_TOKEN fallback. Remove the separate release document and keep the version, merge, and tag instructions in README.
Validation: all 150 tests pass, including 72 shared Python/TypeScript contract cases and new regressions that fail against 1.0.0. Package installation, CJS/ESM identity, TypeScript 5.8/7 consumers, formatting, type checks, and actionlint pass. npm audit reports no vulnerabilities. Public endpoint paths, DTOs, and exact status codes were checked against the core backend.
After merging, tag the merged main commit as v1.0.1 to exercise publishing through OIDC. No release tag is pushed by this PR.