Skip to content

fix: use @supabase/node-fetch #62

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 1 commit into from
Aug 23, 2023
Merged

fix: use @supabase/node-fetch #62

merged 1 commit into from
Aug 23, 2023

Conversation

soedirgo
Copy link
Member

Part of fixing supabase/supabase-js#612

@coveralls
Copy link

coveralls commented Aug 22, 2023 •
edited
Loading

Pull Request Test Coverage Report for Build 5946544857

  • 1 of 3 (33.33%) changed or added relevant lines in 2 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.4%) to 91.739%
Changes Missing Coverage Covered Lines Changed/Added Lines %
src/helper.ts 0 2 0.0%
Totals Coverage Status
Change from base Build 5274036837: -0.4%
Covered Lines: 185
Relevant Lines: 197
💛 - Coveralls

@soedirgo soedirgo force-pushed the fix/supabase-node-fetch branch from 14022b4 to eeb3716 Compare August 23, 2023 03:07
@soedirgo soedirgo merged commit f290bb3 into main Aug 23, 2023
@soedirgo soedirgo deleted the fix/supabase-node-fetch branch August 23, 2023 03:34
@github-actions
Copy link

🎉 This PR is included in version 2.1.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@soedirgo soedirgo mentioned this pull request Sep 5, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@kiwicopple kiwicopple kiwicopple approved these changes

Assignees
No one assigned
Labels
released
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@soedirgo @coveralls @kiwicopple