Skip to content
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.

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

fix: reverted migrate script rename #516

Merged
merged 1 commit into from
Jul 5, 2024

Conversation

fenos
Copy link
Contributor

@fenos fenos commented Jul 5, 2024

What kind of change does this PR introduce?

Bug fix

What is the new behavior?

Revert renaming of the migrate-call.ts file to migrate.ts restoring it to its original
This is because the CLI is hard coding the script name HERE

Fixes #515

@coveralls
Copy link

coveralls commented Jul 5, 2024

Pull Request Test Coverage Report for Build 9806424509

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 79.331%

Totals Coverage Status
Change from base Build 9779826772: 0.0%
Covered Lines: 12948
Relevant Lines: 16187

💛 - Coveralls

@fenos fenos merged commit 8347d13 into master Jul 5, 2024
1 check passed
@fenos fenos deleted the fix/revert-migrate-script-rename branch July 5, 2024 09:54
Copy link

github-actions bot commented Jul 5, 2024

🎉 This PR is included in version 1.6.8 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@Justinyu1618
Copy link

Hey @fenos, how do I get the supabase CLI to pull the latest docker image to get this fix when running supabase db pull?

@Justinyu1618
Copy link

Hey @fenos, how do I get the supabase CLI to pull the latest docker image to get this fix when running supabase db pull?

Never mind, I just deleted the .temp directory inside my supabase folder and reran and it pulled the right image this time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Getting "Cannot find module" after latest docker image pull
4 participants