Skip to content

Conversation

@KhafraDev
Copy link
Member

fixes #4767

it didn't really make sense to throw an error when receiving a 401, did it...

@codecov-commenter
Copy link

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.27%. Comparing base (94d147d) to head (6794380).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4769      +/-   ##
==========================================
+ Coverage   93.26%   93.27%   +0.01%     
==========================================
  Files         109      109              
  Lines       34020    34020              
==========================================
+ Hits        31728    31732       +4     
+ Misses       2292     2288       -4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@mcollina mcollina merged commit be564c1 into nodejs:main Jan 25, 2026
36 of 37 checks passed
@KhafraDev KhafraDev deleted the fix-401-again-please-be-the-last branch January 25, 2026 22:06
@xconverge
Copy link
Contributor

Thanks, glad I wasn't crazy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fetch 401 behavior nodejs

4 participants