chore: set access token explicitly

ydennisy · Apr 1, 2024 · e30b0e5 · e30b0e5
1 parent aba0298
commit e30b0e5
Showing 1 changed file with 9 additions and 9 deletions.
diff --git a/.github/workflows/db-migration.yml b/.github/workflows/db-migration.yml
@@ -3,20 +3,20 @@ name: "[DB] Run migrations"
 on:
   workflow_dispatch: {}
 
-env:
-  SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }}
-  SUPABASE_DB_PASSWORD: ${{ secrets.SUPABASE_DB_PASSWORD }}
-  SUPABASE_PROJECT_ID: fqdoflohofjgariilbzh
-
 jobs:
   migration:
     runs-on: ubuntu-latest
+    env:
+      SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }}
+      SUPABASE_DB_PASSWORD: ${{ secrets.STAGING_DB_PASSWORD }}
+      SUPABASE_PROJECT_ID: fqdoflohofjgariilbzh
+
     steps:
       - uses: actions/checkout@v4
 
       - uses: supabase/setup-cli@v1
+        with:
+          version: latest
 
-      - run: |
-          supabase login --token ${{ env.SUPABASE_ACCESS_TOKEN }}
-          supabase link --project-ref ${{ env.SUPABASE_PROJECT_ID }}
-          supabase db push
+      - run: supabase link --project-ref $SUPABASE_PROJECT_ID
+      - run: supabase db push