✅ When a module is checked, it means:
- Complete File Structure: Every file in
deploy/**/*.sqlhas a corresponding file in bothrevert/**/*.sqlandverify/**/*.sql - Functional Verification: All deploy, revert, and verify operations work properly
- Proper Verification Utilities: The verify scripts use the
pgpm-verifypackage's utilities frompackages/utils/verify - Dependency Requirements: If verification utilities are used,
pgpm-verifyis properly declared as a dependency in the project's control file
- Deploy: Contains the actual SQL changes/additions
- Revert: Contains SQL to undo the deploy changes
- Verify: Contains SQL to verify the changes were applied correctly (should use
pgpm-verifyutilities) - Control File: Must include
pgpm-verifyas a dependency if verification utilities are used
-
packages/data-types/types- Core data types -
packages/data-types/uuid- UUID utilities -
packages/data-types/stamps- Timestamp utilities -
packages/data-types/geotypes- Geographic data types
-
packages/jobs/jobs- Core job system -
packages/jobs/database-jobs- Database-specific job handling
-
packages/metaschema-schema- Database metadata schema and utilities -
packages/metaschema-modules- Module metadata handling -
packages/services- Services schemas for APIs, sites, and domains
-
packages/security/defaults- Security defaults -
packages/security/jwt-claims- JWT claim handling -
packages/security/totp- Time-based One-Time Password (TOTP)
-
packages/security/encrypted-secrets- Encrypted secrets management -
packages/security/encrypted-secrets-table- Table-based encrypted secrets
-
packages/utils/utils- General utility functions -
packages/utils/verify- Verification utilities (used by other modules) -
packages/utils/inflection- String inflection utilities -
packages/utils/base32- Base32 encoding/decoding -
packages/utils/faker- Fake data generation
-
packages/metrics/measurements- Measurement utilities -
packages/metrics/achievements- Achievement system