You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
This pull request removes two changeset files that documented patch updates for the @whatwg-node/node-fetch package. The updates focus on ensuring correct HTTP status codes are returned during redirect handling and when accessing local files via the file:/// protocol (returning 404 or 403 as appropriate). The package’s version has been bumped from 0.7.8 to 0.7.9, and the changelog has been updated to reflect these modifications.
Updated package metadata for version 0.7.9 with changelog entries that detail improvements in redirect handling and local file error management.
Sequence Diagram(s)
sequenceDiagram
participant Client as Client
participant NodeFetch as @whatwg-node/node-fetch
Client->>NodeFetch: Send HTTP request
NodeFetch->>NodeFetch: Check if response requires redirection
NodeFetch-->>Client: Return response with proper HTTP redirect status code (e.g., 301/302)
Loading
sequenceDiagram
participant Client as Client
participant NodeFetch as @whatwg-node/node-fetch
Client->>NodeFetch: Request resource via file:/// URL
NodeFetch->>NodeFetch: Verify file existence and permission
alt File not found
NodeFetch-->>Client: Return 404 error
else Access forbidden
NodeFetch-->>Client: Return 403 error
else File found and accessible
NodeFetch-->>Client: Return file content
end
Hoppity hops across the code,
Patches erased to lighten the load.
Redirects now twirl with proper grace,
File errors show their proper face.
Version 0.7.9 leaps ahead with glee—
A bouncy update from a rabbit (🐰) like me!
📜 Recent review details
Configuration used: CodeRabbit UI Review profile: CHILL Plan: Pro
📥 Commits
Reviewing files that changed from the base of the PR and between 65bba01 and 51c5693.
📒 Files selected for processing (4)
.changeset/few-papayas-fry.md (0 hunks)
.changeset/tough-moles-arrive.md (0 hunks)
packages/node-fetch/CHANGELOG.md (1 hunks)
packages/node-fetch/package.json (1 hunks)
💤 Files with no reviewable changes (2)
.changeset/tough-moles-arrive.md
.changeset/few-papayas-fry.md
🚧 Files skipped from review as they are similar to previous changes (2)
packages/node-fetch/package.json
packages/node-fetch/CHANGELOG.md
⏰ Context from checks skipped due to timeout of 90000ms (18)
GitHub Check: lint
GitHub Check: unit / node 23
GitHub Check: unit / deno
GitHub Check: unit / node 22
GitHub Check: unit / bun
GitHub Check: release-candidate / snapshot
GitHub Check: unit / node 20
GitHub Check: server (undici)
GitHub Check: unit / node 18
GitHub Check: server (ponyfill)
GitHub Check: type check
GitHub Check: node-fetch (consumeBody)
GitHub Check: e2e / azure-function
GitHub Check: server (native)
GitHub Check: e2e / aws-lambda
GitHub Check: esm
GitHub Check: node-fetch (noConsumeBody)
GitHub Check: Analyze (javascript-typescript)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Review comments: Directly reply to a review comment made by CodeRabbit. Example:
I pushed a fix in commit <commit_id>, please review it.
Generate unit testing code for this file.
Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
@coderabbitai generate unit testing code for this file.
@coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
@coderabbitai read src/utils.ts and generate unit testing code.
@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
@coderabbitai help me debug CodeRabbit configuration file.
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.
CodeRabbit Commands (Invoked using PR comments)
@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
Documentation and Community
Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@whatwg-node/node-fetch@0.7.9
Patch Changes
#2049
7c95998Thanks @ardatan! - Redirect with correct status codes
#2051
252f68bThanks @ardatan! - Fix crash on null header values during inspect
#2009
5b5ae5fThanks @ardatan! - When
fetch('file:///...')is used to readfiles;
Summary by CodeRabbit
New Features
Bug Fixes