Remove seed.sql to prevent installationId conflicts

[devin-ai-integration]

Issue

• resolve: N/A

Why is this change needed?

This change removes the seed.sql file which contains a hardcoded GitHub App installationId. When the GitHub App is updated, this ID changes, causing issues in local development environments.

What would you like reviewers to focus on?

Confirm that removing this file is the correct approach to prevent local environment issues with GitHub App authentication.

Testing Verification

Verified that the file has been successfully removed.

Additional Notes

This PR only removes the seed.sql file as requested, with no other changes.

Link to Devin run: https://app.devin.ai/sessions/11ec8e3b59fd471ab71b71af7172309b
Requested by: noritaka.ikeda@route06.co.jp

[changeset-bot]

⚠️ No Changeset found

Latest commit: abc8e45

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
liam-app	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 27, 2025 11:50am
liam-erd-sample	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 27, 2025 11:50am

4 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
liam-docs	⬜️ Ignored (Inspect)	Visit Preview		Mar 27, 2025 11:50am
test-liam-app	⬜️ Ignored (Inspect)			Mar 27, 2025 11:50am
test-liam-docs	⬜️ Ignored (Inspect)			Mar 27, 2025 11:50am
test-liam-erd-sample	⬜️ Ignored (Inspect)			Mar 27, 2025 11:50am

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add "(aside)" to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[supabase]

Updates to Preview Branch (devin/1743075606-remove-seed-sql) ↗︎

Deployments	Status	Updated
Database	✅	Thu, 27 Mar 2025 11:43:09 UTC
Services	✅	Thu, 27 Mar 2025 11:43:09 UTC
APIs	✅	Thu, 27 Mar 2025 11:43:09 UTC

Tasks are run on every commit but only new migration files are pushed.
Close and reopen this PR if you want to apply changes from existing seed or migration files.

Tasks	Status	Updated
Configurations	✅	Thu, 27 Mar 2025 11:43:14 UTC
Migrations	✅	Thu, 27 Mar 2025 11:43:15 UTC
Seeding	✅	Thu, 27 Mar 2025 11:43:15 UTC
Edge Functions	✅	Thu, 27 Mar 2025 11:43:15 UTC

---

View logs for this Workflow Run ↗︎.
Learn more about Supabase for Git ↗︎.

[NoritakaIkeda]

LGTM! I'd love for others to take a look as well!

[MH4GF]

@junkisai cc @NoritakaIkeda It is certainly different from the installation ID of the Local GitHub App, so we should consider supporting it.
Maybe we can adjust it with this setting.
https://supabase.com/docs/guides/deployment/branching#remote-specific-configuration

[junkisai]

@MH4GF @NoritakaIkeda
I see, is my understanding correct as follows? 👀

• seed.sql is also applied to the Preview branch
• Changing the GitHub App settings will cause the installationId to change

[NoritakaIkeda]

@junkisai
My understanding of the latter is the same!

Changing the GitHub App settings will cause the installationId to change

[hoshinotsuyoshi]

nits

If you plan to add similar data inserts again in the future, I’d recommend wrapping them in a BEGIN ... COMMIT transaction and using RETURNING to fetch the inserted IDs instead of hardcoding them.

That way, you can avoid relying on fixed IDs and ensure the data stays consistent even if something fails in the middle of the process.

Example for future reference:

BEGIN;

WITH inserted_project AS (
  INSERT INTO "Project" (name, "updatedAt")
  VALUES ('liam', now())
  RETURNING id
),
inserted_repository AS (
  INSERT INTO "Repository" (name, owner, "installationId", "updatedAt")
  VALUES ('liam', 'liam-hq', 62899121, now())
  RETURNING id
)
INSERT INTO "ProjectRepositoryMapping" ("projectId", "repositoryId", "updatedAt")
SELECT inserted_project.id, inserted_repository.id, now()
FROM inserted_project, inserted_repository;

INSERT INTO "WatchSchemaFilePattern" (pattern, "projectId", "updatedAt")
SELECT 'frontend/packages/db/prisma/**', id, now()
FROM inserted_project;

COMMIT;

No need to change anything this time, just something to keep in mind when adding this kind of data setup again!

[NoritakaIkeda]

@junkisai
The seed.sql file is also applied to the Preview branch, where Supabase automatically runs migrations and seeds for temporary database environments. Since changing GitHub App settings (e.g. reinstalling the app or updating permissions) generates a new installationId.

I'll merge it for now — we can update the seed file later