hermes-fork-is-package-full-rebase-not-viable

When a Python agent framework has been forked so deeply that the fork IS the installed package (no pip install path), a full upstream rebase across 493+ files is impractical and high-risk. The correct strategy is cherry-picking specific feature commits (e.g., web dashboard only) as isolated patches rather than attempting a full merge. Both hermes-consul and oracle-hermes forks hit this pattern on the v0.7.0→v0.9.0 upgrade.

Related

• hermes-sdk-fork-is-package-cherry-pick-only-strategy
• oracle
• docker
• openclaw
• hermes
• openclaw-v45-breaking-config-alias-removal-requires-diff-pas
• large-fork-divergence-means-fork-is-the-package
• dep-bound-images-graphiti-mirofish-hermes-not-optimizable
• uv-over-pip-for-python-2025-projects
• uv-replaces-pip-10-100x-faster-python-monorepo