PostKit v1.2.0 Custom Schema Compatibility Release
Release Notes — v1.2.0
Highlights
Custom Schema Support
PostKit now supports non-public schemas. Import and migrate databases using custom schemas like myapp with postkit db import --schema myapp. Migration tracking is stored in a dedicated postkit schema to avoid polluting your application schema.
Grants Command Removed
The standalone postkit db grants command has been removed. pgschema now manages database grants internally, simplifying the migration workflow to three steps: infra -> migration -> seeds.
Portable Migration Paths
Migration file paths in session.json and committed.json are now stored as project-relative paths. This makes state files portable across machines and team members.
AI-Powered Developer Workflows
PostKit now ships with Claude Code skills and agents for automated development:
- 7 skills:
/create-pr,/write-test-e2e,/write-test-unit,/bugfix,/create-feature,/architecture,/update-docs - 10 agents: reviewer, bugfixer, tester, validator, feature-planner, senior-engineer, architect, docs-agent, e2e-test-agent, unit-test-agent
What's New
postkit db import --schema <name>— import databases with custom schemas- Migration tracking in
postkit.schema_migrationsinstead ofpublic.schema_migrations - Claude Code skills and agents for AI-assisted development
- GitHub Actions release workflow
- Centralized SQL query module
Breaking Changes
postkit db grantsremoved — pgschema handles grants internallygrantsAppliedremoved from session state — existing sessions are backward compatible
Bug Fixes
- Fix schema import leaving temporary
schema.sqlartifacts - Fix deployment step sequence numbering for local clone cleanup
- Fix
pgschema plansearch_path handling for non-public schemas