half-orm-dev 0.18.0a1__tar.gz → 1.0.0a2__tar.gz

{half_orm_dev-0.18.0a1/half_orm_dev.egg-info → half_orm_dev-1.0.0a2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: half_orm_dev
-Version: 0.18.0a1
+Version: 1.0.0a2
 Summary: half_orm development Framework.
 Author-email: Joël Maïzi <joel.maizi@collorg.org>
 License-Expression: GPL-3.0-or-later
@@ -23,7 +23,7 @@ Requires-Dist: GitPython
 Requires-Dist: click
 Requires-Dist: pydash
 Requires-Dist: pytest
-Requires-Dist: half_orm<0.19.0,>=0.18.0
+Requires-Dist: half_orm<1.1.0,>=1.0.0a1
 Requires-Dist: tomli>=2.0.0; python_version < "3.11"
 Requires-Dist: tomli_w>=1.0.0
 Dynamic: license-file
@@ -46,7 +46,7 @@ Modern development workflow for PostgreSQL databases with automatic code generat
 
 ---
 
-## 📖 What is half-orm-dev?
+## What is half-orm-dev?
 
 `half-orm-dev` provides a complete development lifecycle for database-driven applications:
 
@@ -62,9 +62,9 @@ Perfect for teams managing evolving PostgreSQL schemas with Python applications.
 
 ---
 
-## ✨ Key Features
+## Key Features
 
-### 🧪 Systematic Test Validation (Core Safety Feature)
+### Systematic Test Validation (Core Safety Feature)
 
 **Tests run automatically before patch integration and block merges if they fail.**
 
@@ -90,22 +90,22 @@ half_orm dev patch merge
 
 **Cannot be disabled** - it's a core safety feature.
 
-### 🔧 Development Workflow
+### Development Workflow
 
 - **Patch-based development**: Isolated branches for each database change
 - **Automatic code generation**: half-orm Python classes from schema
 - **Complete testing**: Apply patches with full release context
 - **Conflict detection**: Distributed locks prevent concurrent modifications
 
-### 📦 Release Management
+### Release Management
 
 - **Semantic versioning**: patch/minor/major increments
 - **Sequential promotion**: stage → rc → production workflow
 - **Release candidates**: RC validation before production
 - **Hotfix support**: Reopen last released version for urgent fixes
-- **Branch cleanup**: Automatic deletion after promotion
+- **Branch cleanup**: `ho-staged/ID` branches deleted automatically at `release promote prod`
 
-### 🚀 Production
+### Production
 
 - **Safe upgrades**: Automatic database backups before changes
 - **Incremental deployment**: Apply releases sequentially
@@ -114,7 +114,7 @@ half_orm dev patch merge
 
 ---
 
-## 🚀 Installation
+## Installation
 
 ### Prerequisites
 
@@ -136,7 +136,7 @@ half_orm dev --help
 
 ---
 
-## 📖 Quick Start
+## Quick Start
 
 ### Initialize New Project
 
@@ -201,6 +201,7 @@ half_orm dev patch merge
 # → Creates temp validation branch
 # → Runs pytest automatically
 # → If tests pass: merges into ho-release/0.1.0, status → "staged"
+#                  branch renamed: ho-patch/1-users → ho-staged/1-users
 # → If tests fail: aborts, nothing committed
 
 # 9. Promote to production
@@ -210,7 +211,7 @@ half_orm dev release promote prod  # Merge to ho-prod + create tag
 
 ---
 
-## 💻 Core Workflow
+## Core Workflow
 
 ### Branch Strategy
 
@@ -218,18 +219,19 @@ half_orm dev release promote prod  # Merge to ho-prod + create tag
 ho-prod (main production branch)
 │
 ├── ho-release/0.17.0 (integration branch, deleted after prod)
-│   ├── ho-patch/6-feature-x    (temporary, deleted after merge)
-│   ├── ho-patch/7-bugfix-y     (temporary, deleted after merge)
-│   └── ho-patch/8-auth-z       (temporary, deleted after merge)
+│   ├── ho-patch/6-feature-x    → ho-staged/6-feature-x  (after merge)
+│   ├── ho-patch/7-bugfix-y     → ho-staged/7-bugfix-y   (after merge)
+│   └── ho-patch/8-auth-z       → ho-staged/8-auth-z     (after merge)
 │
 └── ho-release/0.18.0 (next version in parallel)
-    └── ho-patch/10-new-api     (temporary, deleted after merge)
+    └── ho-patch/10-new-api     (in development)
 ```
 
 **Branch Types:**
 - **ho-prod**: Stable production branch (source of truth)
-- **ho-release/X.Y.Z**: Integration branches (temporary)
-- **ho-patch/ID**: Patch development branches (temporary)
+- **ho-release/X.Y.Z**: Integration branches (temporary, deleted after prod)
+- **ho-patch/ID**: Patch development branches (renamed to `ho-staged/ID` after merge)
+- **ho-staged/ID**: Staged patch branches (preserved for debugging, deleted at `release promote prod`)
 
 ### Release Files
 
@@ -258,6 +260,8 @@ ho-prod (main production branch)
 │ 3. patch apply             Apply & test changes             │
 │ 4. patch merge             Merge into release (TESTS!)      │
 │                            ✅ Tests pass → integrated       │
+│                               branch: ho-patch/X →          │
+│                                       ho-staged/X           │
 │                            ❌ Tests fail → aborted          │
 │                                                             │
 │ RELEASE PROMOTION                                           │
@@ -277,7 +281,7 @@ ho-prod (main production branch)
 
 ---
 
-## 📖 Command Reference
+## Command Reference
 
 ### Init & Clone
 
@@ -301,6 +305,33 @@ half_orm dev check --dry-run
 
 **Note:** This command runs automatically before other commands (git hooks, configuration, stale branches cleanup).
 
+When a newer version of `half-orm-dev` is available, the output includes a link to the PyPI release page where you can review breaking changes before upgrading.
+
+### Migrate
+
+When `half-orm-dev` is updated, run `migrate` once to apply any repository migrations:
+
+```bash
+half_orm dev migrate
+```
+
+If the new version introduces **breaking changes**, they are displayed before the confirmation prompt and you must type `yes` (not just `y`) to proceed:
+
+```
+╔══════════════════════════════════════════════════╗
+║              BREAKING CHANGES                    ║
+╚══════════════════════════════════════════════════╝
+
+--- half-orm-dev 1.0.0 ---
+# hop 1.0.0 — Breaking Changes
+...
+
+Type "yes" to confirm you have read the breaking changes and want to proceed.
+Proceed? [no]:
+```
+
+For non-breaking upgrades a standard `y/n` prompt is shown instead.
+
 ### Release Commands
 
 A release must be created before creating patches.
@@ -381,7 +412,7 @@ These files are automatically:
 
 ---
 
-## 🎯 Example: Team Collaboration
+## Example: Team Collaboration
 
 ```bash
 # Integration Manager: Create release
@@ -394,6 +425,7 @@ half_orm dev patch create 456-dashboard
 git checkout ho-patch/456-dashboard
 half_orm dev patch merge  # Tests run automatically
 # → Status: "staged" in 0.17.0-patches.toml
+# → Branch renamed: ho-patch/456-dashboard → ho-staged/456-dashboard
 
 # Developer B: Sync and create patch
 git checkout ho-release/0.17.0
@@ -409,7 +441,7 @@ half_orm dev patch merge
 
 ---
 
-## 🎓 Development Philosophy
+## Development Philosophy
 
 half-orm-dev combines **Domain-Driven Design** with **Test-Driven Development**, integrated into Git:
 
@@ -423,7 +455,7 @@ This approach ensures that every schema change is tested in the full release con
 
 ---
 
-## 📚 Documentation
+## Documentation
 
 - **[CONTRIBUTING.md](CONTRIBUTING.md)** - Development setup, testing, contribution guidelines
 - **[docs/ARCHITECTURE.md](docs/ARCHITECTURE.md)** - Technical architecture and implementation details
@@ -433,7 +465,7 @@ For detailed technical documentation, see [docs/ARCHITECTURE.md](docs/ARCHITECTU
 
 ---
 
-## 🔧 Troubleshooting
+## Troubleshooting
 
 ### Error: "Must be on ho-release/* branch"
 ```bash
@@ -519,7 +551,7 @@ For more troubleshooting, see [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md).
 
 ---
 
-## 🤝 Contributing
+## Contributing
 
 Contributions are welcome! See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup and guidelines.
 
@@ -545,7 +577,7 @@ pytest -m integration       # Integration tests only
 
 ---
 
-## 📞 Getting Help
+## Getting Help
 
 - **Issues**: [GitHub Issues](https://github.com/half-orm/half-orm-dev/issues)
 - **Documentation**: [CONTRIBUTING.md](CONTRIBUTING.md) and [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md)
@@ -553,10 +585,6 @@ pytest -m integration       # Integration tests only
 
 ---
 
-## 📄 License
-
-This project is licensed under the GNU General Public License v3.0 - see the [LICENSE](LICENSE) file for details.
-
----
+## License
 
-**Made with ❤️ by the half-orm team**
+This project is licensed under the [GPL-3.0](LICENSE) license.

{half_orm_dev-0.18.0a1 → half_orm_dev-1.0.0a2}/README.md

@@ -15,7 +15,7 @@ Modern development workflow for PostgreSQL databases with automatic code generat
 
 ---
 
-## 📖 What is half-orm-dev?
+## What is half-orm-dev?
 
 `half-orm-dev` provides a complete development lifecycle for database-driven applications:
 
@@ -31,9 +31,9 @@ Perfect for teams managing evolving PostgreSQL schemas with Python applications.
 
 ---
 
-## ✨ Key Features
+## Key Features
 
-### 🧪 Systematic Test Validation (Core Safety Feature)
+### Systematic Test Validation (Core Safety Feature)
 
 **Tests run automatically before patch integration and block merges if they fail.**
 
@@ -59,22 +59,22 @@ half_orm dev patch merge
 
 **Cannot be disabled** - it's a core safety feature.
 
-### 🔧 Development Workflow
+### Development Workflow
 
 - **Patch-based development**: Isolated branches for each database change
 - **Automatic code generation**: half-orm Python classes from schema
 - **Complete testing**: Apply patches with full release context
 - **Conflict detection**: Distributed locks prevent concurrent modifications
 
-### 📦 Release Management
+### Release Management
 
 - **Semantic versioning**: patch/minor/major increments
 - **Sequential promotion**: stage → rc → production workflow
 - **Release candidates**: RC validation before production
 - **Hotfix support**: Reopen last released version for urgent fixes
-- **Branch cleanup**: Automatic deletion after promotion
+- **Branch cleanup**: `ho-staged/ID` branches deleted automatically at `release promote prod`
 
-### 🚀 Production
+### Production
 
 - **Safe upgrades**: Automatic database backups before changes
 - **Incremental deployment**: Apply releases sequentially
@@ -83,7 +83,7 @@ half_orm dev patch merge
 
 ---
 
-## 🚀 Installation
+## Installation
 
 ### Prerequisites
 
@@ -105,7 +105,7 @@ half_orm dev --help
 
 ---
 
-## 📖 Quick Start
+## Quick Start
 
 ### Initialize New Project
 
@@ -170,6 +170,7 @@ half_orm dev patch merge
 # → Creates temp validation branch
 # → Runs pytest automatically
 # → If tests pass: merges into ho-release/0.1.0, status → "staged"
+#                  branch renamed: ho-patch/1-users → ho-staged/1-users
 # → If tests fail: aborts, nothing committed
 
 # 9. Promote to production
@@ -179,7 +180,7 @@ half_orm dev release promote prod  # Merge to ho-prod + create tag
 
 ---
 
-## 💻 Core Workflow
+## Core Workflow
 
 ### Branch Strategy
 
@@ -187,18 +188,19 @@ half_orm dev release promote prod  # Merge to ho-prod + create tag
 ho-prod (main production branch)
 │
 ├── ho-release/0.17.0 (integration branch, deleted after prod)
-│   ├── ho-patch/6-feature-x    (temporary, deleted after merge)
-│   ├── ho-patch/7-bugfix-y     (temporary, deleted after merge)
-│   └── ho-patch/8-auth-z       (temporary, deleted after merge)
+│   ├── ho-patch/6-feature-x    → ho-staged/6-feature-x  (after merge)
+│   ├── ho-patch/7-bugfix-y     → ho-staged/7-bugfix-y   (after merge)
+│   └── ho-patch/8-auth-z       → ho-staged/8-auth-z     (after merge)
 │
 └── ho-release/0.18.0 (next version in parallel)
-    └── ho-patch/10-new-api     (temporary, deleted after merge)
+    └── ho-patch/10-new-api     (in development)
 ```
 
 **Branch Types:**
 - **ho-prod**: Stable production branch (source of truth)
-- **ho-release/X.Y.Z**: Integration branches (temporary)
-- **ho-patch/ID**: Patch development branches (temporary)
+- **ho-release/X.Y.Z**: Integration branches (temporary, deleted after prod)
+- **ho-patch/ID**: Patch development branches (renamed to `ho-staged/ID` after merge)
+- **ho-staged/ID**: Staged patch branches (preserved for debugging, deleted at `release promote prod`)
 
 ### Release Files
 
@@ -227,6 +229,8 @@ ho-prod (main production branch)
 │ 3. patch apply             Apply & test changes             │
 │ 4. patch merge             Merge into release (TESTS!)      │
 │                            ✅ Tests pass → integrated       │
+│                               branch: ho-patch/X →          │
+│                                       ho-staged/X           │
 │                            ❌ Tests fail → aborted          │
 │                                                             │
 │ RELEASE PROMOTION                                           │
@@ -246,7 +250,7 @@ ho-prod (main production branch)
 
 ---
 
-## 📖 Command Reference
+## Command Reference
 
 ### Init & Clone
 
@@ -270,6 +274,33 @@ half_orm dev check --dry-run
 
 **Note:** This command runs automatically before other commands (git hooks, configuration, stale branches cleanup).
 
+When a newer version of `half-orm-dev` is available, the output includes a link to the PyPI release page where you can review breaking changes before upgrading.
+
+### Migrate
+
+When `half-orm-dev` is updated, run `migrate` once to apply any repository migrations:
+
+```bash
+half_orm dev migrate
+```
+
+If the new version introduces **breaking changes**, they are displayed before the confirmation prompt and you must type `yes` (not just `y`) to proceed:
+
+```
+╔══════════════════════════════════════════════════╗
+║              BREAKING CHANGES                    ║
+╚══════════════════════════════════════════════════╝
+
+--- half-orm-dev 1.0.0 ---
+# hop 1.0.0 — Breaking Changes
+...
+
+Type "yes" to confirm you have read the breaking changes and want to proceed.
+Proceed? [no]:
+```
+
+For non-breaking upgrades a standard `y/n` prompt is shown instead.
+
 ### Release Commands
 
 A release must be created before creating patches.
@@ -350,7 +381,7 @@ These files are automatically:
 
 ---
 
-## 🎯 Example: Team Collaboration
+## Example: Team Collaboration
 
 ```bash
 # Integration Manager: Create release
@@ -363,6 +394,7 @@ half_orm dev patch create 456-dashboard
 git checkout ho-patch/456-dashboard
 half_orm dev patch merge  # Tests run automatically
 # → Status: "staged" in 0.17.0-patches.toml
+# → Branch renamed: ho-patch/456-dashboard → ho-staged/456-dashboard
 
 # Developer B: Sync and create patch
 git checkout ho-release/0.17.0
@@ -378,7 +410,7 @@ half_orm dev patch merge
 
 ---
 
-## 🎓 Development Philosophy
+## Development Philosophy
 
 half-orm-dev combines **Domain-Driven Design** with **Test-Driven Development**, integrated into Git:
 
@@ -392,7 +424,7 @@ This approach ensures that every schema change is tested in the full release con
 
 ---
 
-## 📚 Documentation
+## Documentation
 
 - **[CONTRIBUTING.md](CONTRIBUTING.md)** - Development setup, testing, contribution guidelines
 - **[docs/ARCHITECTURE.md](docs/ARCHITECTURE.md)** - Technical architecture and implementation details
@@ -402,7 +434,7 @@ For detailed technical documentation, see [docs/ARCHITECTURE.md](docs/ARCHITECTU
 
 ---
 
-## 🔧 Troubleshooting
+## Troubleshooting
 
 ### Error: "Must be on ho-release/* branch"
 ```bash
@@ -488,7 +520,7 @@ For more troubleshooting, see [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md).
 
 ---
 
-## 🤝 Contributing
+## Contributing
 
 Contributions are welcome! See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup and guidelines.
 
@@ -514,7 +546,7 @@ pytest -m integration       # Integration tests only
 
 ---
 
-## 📞 Getting Help
+## Getting Help
 
 - **Issues**: [GitHub Issues](https://github.com/half-orm/half-orm-dev/issues)
 - **Documentation**: [CONTRIBUTING.md](CONTRIBUTING.md) and [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md)
@@ -522,10 +554,6 @@ pytest -m integration       # Integration tests only
 
 ---
 
-## 📄 License
-
-This project is licensed under the GNU General Public License v3.0 - see the [LICENSE](LICENSE) file for details.
-
----
+## License
 
-**Made with ❤️ by the half-orm team**
+This project is licensed under the [GPL-3.0](LICENSE) license.

{half_orm_dev-0.18.0a1 → half_orm_dev-1.0.0a2}/half_orm_dev/cli/commands/check.py

@@ -86,6 +86,9 @@ def _display_check_results(repo, result: dict, dry_run: bool, verbose: bool):
             click.echo(f"Latest version:  {utils.Color.green(utils.Color.bold(latest))}")
             click.echo()
             click.echo(f"To update, run: {utils.Color.bold('pip install --upgrade half_orm_dev')}")
+            click.echo()
+            click.echo(f"Before upgrading, check for breaking changes:")
+            click.echo(f"  https://pypi.org/project/half-orm-dev/{latest}/")
             click.echo(f"{'='*70}")
             click.echo()
 

{half_orm_dev-0.18.0a1 → half_orm_dev-1.0.0a2}/half_orm_dev/cli/commands/migrate.py

@@ -7,6 +7,7 @@ is newer than the repository's hop_version in .hop/config.
 
 import click
 from half_orm_dev.repo import Repo, RepoError
+from half_orm_dev.migration_manager import MigrationManager
 from half_orm import utils
 
 
@@ -75,15 +76,52 @@ def migrate(verbose: bool) -> None:
         click.echo(f"  Current branch: {current_branch}")
         click.echo()
 
+        # Check for breaking changes between current and target version
+        mgr = MigrationManager(repo)
+        breaking_changes = mgr.get_breaking_changes(config_version, installed_version)
+
+        needs_explicit_confirm = False
+        if breaking_changes:
+            import importlib.metadata
+            try:
+                half_orm_installed = importlib.metadata.version('half-orm')
+            except importlib.metadata.PackageNotFoundError:
+                half_orm_installed = None
+
+            width = 70
+            lines = []
+            lines.append('━' * width)
+            lines.append(f"  ⚠️  BREAKING CHANGES")
+            lines.append('━' * width)
+            for bc in breaking_changes:
+                if bc['component'] == 'hop':
+                    label = 'half-orm-dev'
+                    display_version = installed_version
+                else:
+                    label = 'half-orm'
+                    display_version = half_orm_installed or bc['version']
+                lines.append(f"\n  ━━━ {label} {display_version} {'━' * max(0, width - len(label) - len(display_version) - 7)}")
+                for line in bc['content'].splitlines():
+                    lines.append(f"  {line}")
+            lines.append(f"\n{'━' * width}")
+            click.echo_via_pager('\n'.join(lines) + '\n')
+            needs_explicit_confirm = True
 
         # Run migrations
-        if not click.confirm("Do you want to proceed?", default=False):
+        if needs_explicit_confirm:
+            click.echo("Type \"yes\" to confirm you have read the breaking changes and want to proceed.")
+            answer = click.prompt("Proceed?", default="no")
+            confirmed = answer.strip().lower() == "yes"
+        else:
+            confirmed = click.confirm("Do you want to proceed?", default=False)
+
+        if not confirmed:
             click.echo()
             click.echo("If you want to revert half_orm_dev run:")
             click.echo(f"  pip install half-orm-dev=={config_version}")
         else:
             try:
-                click.echo(f"  Running migrations...")
+                click.echo("  Running migrations...")
                 result = repo.run_migrations_if_needed(silent=False)
 
                 if result['migration_run']: