Skip to content

Conversation

@pyramation
Copy link
Contributor

@pyramation pyramation commented Dec 14, 2025

feat: rebrand PGPM packages from @launchql/* to @pgpmjs/*

Summary

This PR implements the comprehensive rebranding strategy outlined in rebranding.md, renaming PGPM (PostgreSQL Package Manager) packages from the @launchql/* npm scope to @pgpmjs/*.

Package renames (7 packages):

  • @launchql/core@pgpmjs/core
  • @launchql/env@pgpmjs/env
  • @launchql/types@pgpmjs/types
  • @launchql/logger@pgpmjs/logger
  • @launchql/server-utils@pgpmjs/server-utils
  • @launchql/client@pgpmjs/client
  • @launchql/orm@pgpmjs/orm

Class/type renames: LaunchQLPackagePgpmPackage, LaunchQLMigratePgpmMigrate, LaunchQLInitPgpmInit, LaunchQLErrorPgpmError, LaunchQLOptionsPgpmOptions, LaunchQLWorkspaceConfigPgpmWorkspaceConfig

File renames: launchql.tspgpm.ts in both types and core packages

⚠️ Breaking change: No backward compatibility. All code must use the new Pgpm* names directly. Old names (LaunchQLPackage, LaunchQLOptions, etc.) are no longer exported.

Updates since last revision

  • Removed all backward-compatible re-exports per user request
  • Updated ALL internal usages to use Pgpm* names directly (no more LaunchQL* references in PGPM packages)
  • Fixed remaining LaunchQLOptionsPgpmOptions in graphile-settings, explorer, server, cli, and env packages
  • Fixed LaunchQLInit, LaunchQLMigrate, LaunchQLErrorPgpmInit, PgpmMigrate, PgpmError in pgpm CLI commands

Review & Testing Checklist for Human

  • Verify all LaunchQL references are gone from PGPM packages* - Run grep -r "LaunchQL" packages/ --include="*.ts" | grep -v "node_modules" | grep -v "dist" and confirm only comments/strings remain (not type/class usages)
  • Run full test suite with database - Local testing couldn't run DB-dependent tests; CI should verify (pnpm test)
  • Test pgpm CLI commands - Run pgpm deploy, pgpm revert, pgpm verify in a sandbox to confirm they work with new class names
  • Check sandbox files - Some sandbox test files still reference LaunchQLProject which may need updating or may be intentionally separate

Recommended test plan:

  1. Run pnpm test across the workspace in CI environment with PostgreSQL
  2. Test the pgpm CLI commands (deploy, revert, verify) in a sandbox environment
  3. Verify imports from @pgpmjs/core export PgpmPackage (not LaunchQLPackage)

Notes

  • ~200 files changed across the codebase
  • LaunchQL-branded packages (graphile plugins, server, explorer, launchql-gen, etc.) remain as @launchql/* but now import types from @pgpmjs/types
  • This is a clean upgrade with no backward compatibility as requested

Link to Devin run: https://app.devin.ai/sessions/dba689d603e94f1f9eb4b12895bd14a7
Requested by: Dan Lynch ([email protected]) / @pyramation

pyramation and others added 2 commits December 13, 2025 15:47
This commit implements the comprehensive rebranding strategy as outlined in rebranding.md:

Package Renames:
- @launchql/core -> @pgpmjs/core
- @launchql/env -> @pgpmjs/env
- @launchql/types -> @pgpmjs/types
- @launchql/logger -> @pgpmjs/logger
- @launchql/server-utils -> @pgpmjs/server-utils
- @launchql/client -> @pgpmjs/client
- @launchql/orm -> @pgpmjs/orm

Class/Type Renames:
- LaunchQLPackage -> PgpmPackage
- LaunchQLMigrate -> PgpmMigrate
- LaunchQLInit -> PgpmInit
- LaunchQLError -> PgpmError
- LaunchQLOptions -> PgpmOptions
- LaunchQLWorkspaceConfig -> PgpmWorkspaceConfig
- LaunchQLMigrateOptions -> PgpmMigrateOptions

File Renames:
- packages/types/src/launchql.ts -> packages/types/src/pgpm.ts
- packages/core/src/core/class/launchql.ts -> packages/core/src/core/class/pgpm.ts

Function Renames:
- resolveLaunchqlPath -> resolvePgpmPath

Backward Compatibility:
- Added deprecated re-exports for all renamed classes and types
- Old names still work but will show deprecation warnings

All import statements and package.json dependencies have been updated across the entire codebase.

Co-Authored-By: Dan Lynch <[email protected]>
@devin-ai-integration
Copy link
Contributor

🤖 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

devin-ai-integration bot and others added 4 commits December 14, 2025 00:11
Updated test files and test-utils to use:
- PgpmPackage instead of LaunchQLPackage
- PgpmMigrate instead of LaunchQLMigrate
- Import from '../src/core/class/pgpm' instead of '../src/core/class/launchql'

Co-Authored-By: Dan Lynch <[email protected]>
…ences to Pgpm*

- Removed all backward-compatible re-exports from core, types, and env packages
- Updated all LaunchQLOptions -> PgpmOptions across entire codebase
- Updated all LaunchQLPackage -> PgpmPackage usages
- Updated all LaunchQLMigrate -> PgpmMigrate usages
- Updated all LaunchQLInit -> PgpmInit usages
- Updated all LaunchQLError -> PgpmError usages

This is a clean upgrade with no backward compatibility as requested.

Co-Authored-By: Dan Lynch <[email protected]>
- Fixed LaunchQLMigrate -> PgpmMigrate in CLI test-utils
- Updated error messages in pgpm commands to say 'PGPM' instead of 'LaunchQL'
- Fixed LaunchQLProject -> PgpmPackage in sandbox test files

Co-Authored-By: Dan Lynch <[email protected]>
@pyramation pyramation changed the base branch from feat/rebrand to main December 14, 2025 01:07
- Updated add-functionality.test.ts to expect 'PGPM' instead of 'LaunchQL' in error message
- Removed obsolete LaunchQLPackage.writeModulePlan snapshots (now PgpmPackage)

Co-Authored-By: Dan Lynch <[email protected]>
@pyramation pyramation closed this Dec 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants