feat: change public schema to trueforge schema for Postgres - #488
Open
thesujai wants to merge 2 commits into
Open
feat: change public schema to trueforge schema for Postgres#488thesujai wants to merge 2 commits into
thesujai wants to merge 2 commits into
Conversation
thesujai
requested review from
bhaveshpatel640,
chiragjn,
debajyoti-truefoundry,
heerambavi1998 and
sr07asthana
as code owners
August 28, 2026 13:06
🦋 Changeset detectedLatest commit: eae5777 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit cdca799. Configure here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
change public schema to trueforge schema for Postgres
Changes
change public schema to trueforge schema for Postgres
How was this tested?
Recreating every scenarios and also through tests
Checklist
pnpm build,pnpm test,pnpm typecheck,pnpm lint:ci, andpnpm format:checkpass locallypackages/trueforge-sdk,.github/fern/openapi/openapi.json,docs/openapi.json) — fork PRs omit SDK regen; maintainers regenerate after merge.env.exampleupdated if configuration or behavior changedNote
Medium Risk
One-time DDL on every migration run (schema create + possible table moves) affects all Postgres deployments; logic is tested but mistakes could strand tables or break migrations.
Overview
Moves Trueforge’s Postgres app data and Kysely migration bookkeeping out of
publicinto a dedicatedtrueforgeschema.Migration path:
runMigrationsnow callsensureTrueforgeSchemafirst, which creates the schema (with an advisory lock andlock_timeout), thenALTER TABLE … SET SCHEMAfor a fixed list of legacypublictables so existing installs keep data and migration history. The KyselyMigratorusesmigrationTableSchema: trueforge.Runtime:
createDbsets the poolsearch_pathtotrueforgeso unqualified queries hit the right tables. AGENTS.md documents the convention.Tests: Client test asserts
search_path; new integration tests cover greenfield installs and simulating pre-upgradepublictables moved back on upgrade.Reviewed by Cursor Bugbot for commit eae5777. Bugbot is set up for automated code reviews on this repo. Configure here.