Skip to content

docs(fork): track custom patches and safe upstream upgrade procedure - #48

Merged
Bl0ck154 merged 4 commits into
productionfrom
docs/fork-upstream-upgrade-register-20261024
Oct 24, 2026
Merged

Bl0ck154 merged 4 commits into
productionfrom
docs/fork-upstream-upgrade-register-20261024

Conversation

@Bl0ck154

Copy link
Copy Markdown
Owner

Purpose

Make the fork's custom patches and future official-upstream upgrade process discoverable to every agent, without touching running production.

Added

Critical finding

GitHub cross-fork compare on 2026-10-24: Bl0ck154/OmniRoute:production 151 commits ahead and 2,171 commits behind cheaper-inference/OmniRoute:release/v3.8.53. A blind "Sync fork" / hard reset would discard custom changes. Upgrading is feasible through a dedicated integration branch, but needs conflict resolution and regression testing.

Safety

Docs/agent guidance only, no runtime file, Docker/Next build, CI/release workflow or VPS changes. Do not deploy solely because these documents are merged. Verified updater rollback restores a previous package but does not automatically roll back SQLite migrations. No credentials or private logs included.

@Bl0ck154
Bl0ck154 merged commit 826a726 into production Oct 24, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant