Skip to content

fix: log correct response status #48

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 3 commits into from
Dec 11, 2024
Merged

fix: log correct response status #48

merged 3 commits into from
Dec 11, 2024

Conversation

@achingbrain
Copy link
Member

@achingbrain achingbrain commented Dec 11, 2024

When the second request fails, log the status of the second request, not the first.

Change checklist

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation if necessary (this includes comments as well)
  • I have added tests that prove my fix is effective or that my feature works

@achingbrain
fix: log correct response status
f1f1b20 
When the second request fails, log the status of the second request, not the first.
@achingbrain
chore: fix build
58c4088
@achingbrain
chore: fix ci
40e2955
@achingbrain achingbrain merged commit e23855b into main Dec 11, 2024
21 checks passed
github-actions bot pushed a commit that referenced this pull request Dec 11, 2024
@semantic-release-bot
chore(release): 2.1.1 [skip ci]
9f23d3c 
## [2.1.1](v2.1.0...v2.1.1) (2024-12-11)

### Bug Fixes

* log correct response status ([#48](#48)) ([e23855b](e23855b))

### Dependencies

* bump @multiformats/multiaddr-to-uri from 10.1.2 to 11.0.0 ([#46](#46)) ([a7960e6](a7960e6))
@github-actions
Copy link

github-actions bot commented Dec 11, 2024

🎉 This PR is included in version 2.1.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Reviewers

No reviews

Assignees

No one assigned

Labels

released

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@achingbrain