uql-orm 0.2.4 → 0.2.6

package/CHANGELOG.md

@@ -1,9 +1,33 @@
+# Change Log
+
+All notable changes to this project will be documented in this file.
+See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
+
+## [0.2.6](https://github.com/rogerpadilla/uql/compare/uql-orm@0.2.5...uql-orm@0.2.6) (2026-03-11)
+
+
+### Features
+
+* Introduce a new cursive "U" logo in SVG, PNG, and JPG formats, and update package dependencies. ([073239b](https://github.com/rogerpadilla/uql/commit/073239b2342eecc96b15f5099d0f9b18a7a4cf23))
+
+
+
+
+
 # Changelog
 
 All notable changes to this project will be documented in this file. Please add new changes to the top.
 
 date format is [yyyy-mm-dd]
 
+## [0.2.6] - 2026-03-11
+### Documentation
+- **README – Migrations & Synchronization**: Rewrote the section with an entity-first intro explaining that UQL auto-generates migrations from entities. Reordered CLI commands to lead with `generate:entities`, renumbered usage examples, and added a concrete quick-start snippet.
+
+## [0.2.5] - 2026-03-11
+### Branding
+- **New Logo**: Introduced a new cursive "U" logo in indigo (`#4F46E5`). Available in SVG, PNG, and JPG formats under `assets/`.
+
 ## [0.2.4] - 2026-03-10
 ### Bug Fixes
 - **ManyToOne / OneToOne relation filtering**: `$where` clauses referencing `m1` or `11` relations (e.g., `{ item: { name: 'Widget' } }`) now correctly generate `EXISTS` subqueries. Previously, these cardinalities were unhandled and fell through to `compareFieldOperator`, throwing an "unknown operator" error. The `compareRelation` method now supports all four cardinalities (`mm`, `1m`, `m1`, `11`) with direction-aware join resolution.

package/README.md

@@ -446,13 +446,28 @@ try {
 
 ## 5. Migrations & Synchronization
 
+UQL takes an **Entity-First** approach: you modify your TypeScript entity classes, and UQL auto-generates the migration files for you. No need to write DDL manually — UQL diffs your entities against the live database and generates the exact SQL needed.
+
+```bash
+# 1. Update your entity (add a field, change a type, add a relation...)
+# 2. Auto-generate the migration
+npx uql-migrate generate:entities add_user_nickname
+
+# 3. Review and apply
+npx uql-migrate up
+```
+
+> **Your entities are the single source of truth.** Want manual migrations for data backfills or custom SQL? You can do that too — full automation + full control when you need it.
+
 ### 1. Unified Configuration
 
-Ideally, use the same `uql.config.ts` for your application bootstrap and the CLI:
+Reuse the same `uql.config.ts` for your app and the CLI to ensure consistent settings (naming strategies, entities, pool):
 
 ```ts
 // uql.config.ts
 import type { Config } from 'uql-orm';
+import { PgQuerierPool } from 'uql-orm/postgres';
+import { User, Profile, Post } from './entities';
 
 export default {
   pool: new PgQuerierPool({ /* ... */ }),
@@ -461,17 +476,15 @@ export default {
 } satisfies Config;
 ```
 
-**Why?** Using a single config for both your app and the CLI is recommended for consistency. It prevents bugs where your runtime uses one naming strategy (e.g. `camelCase`) but your migrations use another (e.g. `snake_case`), or where the CLI isn't aware of all your entities. It enforces a Single Source of Truth for your database connection and schema.
-
 ### 2. Manage via CLI
 
 Use the CLI to manage your database schema evolution.
 
 | Command | Description |
 | :--- | :--- |
-| `generate:from-db` | **Scaffolds Entities** from an existing database. Includes **Smart Relation Detection**. |
-| `generate <name>` | Creates an empty timestamped file for **manual** SQL migrations (e.g., data backfills). |
 | `generate:entities <name>` | **Auto-generates** a migration by diffing your entities against the current DB schema. |
+| `generate <name>` | Creates an empty timestamped file for **manual** SQL migrations (e.g., data backfills). |
+| `generate:from-db` | **Scaffolds Entities** from an existing database. Includes **Smart Relation Detection**. |
 | `drift:check` | **Drift Detection**: Compares your defined entities against the actual database schema and reports discrepancies. |
 | `up` | Applies all pending migrations. |
 | `down` | Rolls back the last applied migration batch. |
@@ -480,20 +493,20 @@ Use the CLI to manage your database schema evolution.
 #### Usage Examples
 
 ```bash
-# 1. Create a manual migration
-npx uql-migrate generate seed_default_roles
-
-# 2. Auto-generate schema changes from your code
+# 1. Auto-generate schema changes from your entities
 npx uql-migrate generate:entities add_profile_table
 
-# 3. Apply changes
+# 2. Apply changes
 npx uql-migrate up
 
-# 4. Check for schema drift (Production Safety)
+# 3. Check for schema drift (Production Safety)
 npx uql-migrate drift:check
 
-# 5. Scaffold entities from an existing DB (Legacy Adoption)
+# 4. Scaffold entities from an existing DB (Legacy Adoption)
 npx uql-migrate generate:from-db --output ./src/entities
+
+# 5. Create a manual migration (for data backfills or custom SQL)
+npx uql-migrate generate seed_default_roles
 ```
 
 > **Bun Users**: If your `uql.config.ts` uses TypeScript path aliases (e.g., `~app/...`), run migrations with the `--bun` flag to ensure proper resolution:

package/package.json

@@ -3,7 +3,7 @@
   "homepage": "https://uql-orm.dev",
   "description": "One Language. Frontend to Backend.",
   "license": "MIT",
-  "version": "0.2.4",
+  "version": "0.2.6",
   "type": "module",
   "sideEffects": false,
   "main": "./dist/index.js",
@@ -142,5 +142,5 @@
   "publishConfig": {
     "access": "public"
   },
-  "gitHead": "72dc289935a239ac31ab3e0fd79dfd693da9d8a7"
+  "gitHead": "944abbbccc7bc03b863a979c08e67c7d37fd506b"
 }