Prepare clearfetch 1.0.8 release - #51
Merged
Merged
Conversation
- validate base URLs, timeouts, response types, and JSON parsers when clients are created - reuse request normalizers and cover invalid defaults with client tests
- accept object and array results from npm pack and npm view - fail clearly when package metadata has no usable record
- freeze normalized object queries once and reuse them for hook metadata and retry contexts\n- preserve defensive copying for direct hook-option inputs and cover frozen query behavior
- centralize response-mode overloads for reusable clients\n- cover non-default response types across client methods and TypeScript 5 compatibility
- document client-default validation timing and record the unreleased declaration changes\n- use lifecycle-disabled installs and integrity/provenance release verification
- bound stalled and oversized error-body diagnostics without splitting Unicode\n- support promise-based JSON parsers while preserving timeout classification\n- validate abort signals and cover cross-realm native signals
- retry transient npm registry and attestation visibility gaps with request deadlines\n- keep integrity mismatches and terminal registry failures fatal\n- remove failed pack-smoke tarballs and cover both release safeguards
- describe bounded error-body capture and async parser behavior\n- document abort-signal validation and cross-realm support\n- record bounded post-publish verification retries
Promote the unreleased runtime, type-surface, diagnostic, and release-hardening changes into the 1.0.8 changelog and synchronize package metadata.
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
Prepare the backward-compatible runtime, type-surface, diagnostic, and release-hardening changes on
mainfor the1.0.8patch release.Unreleasedentries to1.0.8package.jsonandpackage-lock.jsonto1.0.8Validation
npm run check:lockfilenpm run lintnpm test— 163 passednpm run test:browser-like— 3 passednpm run test:browser-real— 1 passednpm run buildnpm run test:types-compatnpm run check:package-metadatanpm run check:dependency-audit— 0 vulnerabilitiesnpm run check:dependency-signaturesnpm run check:pack-smoke -- --retainnpm run check:publish-dry-run -- release-artifact/gavoryn-clearfetch-1.0.8.tgzgit diff --checkAfter merge, create the annotated
v1.0.8tag on the synchronizedmaincommit and let.github/workflows/release.ymlpublish and verify the exact artifact.