Skip to content

chore!: switch dependency from eyrie to flux - #308

Merged
Patel230 merged 2 commits into
mainfrom
chore/deps-flux-rename
Sep 15, 2026
Merged

Patel230 merged 2 commits into
mainfrom
chore/deps-flux-rename

Conversation

@Patel230

Copy link
Copy Markdown
Contributor

Summary

  • rho now depends on github.com/GrayCodeAI/flux v0.0.1 (provider runtime renamed from eyrie; old eyrie tags/releases were removed, so the old pin is unresolvable for fresh checkouts)
  • All 31 production files' import paths migrated; type aliases renamed (EyrieMessageFluxMessage, etc.) to match flux's actual API
  • Env vars renamed: EYRIE_CONFIG_DIRFLUX_CONFIG_DIR, EYRIE_MODEL_CATALOG_PATHFLUX_MODEL_CATALOG_PATH
  • User state path moved: ~/.../eyrie/provider.json~/.../flux/provider.json
  • Boundary-guard scripts, ecosystem manifest, CI composite action, lefthook targets, docs, golden help snapshots, and compatibility matrix all updated

BREAKING CHANGE

Dependency module path changed; env vars renamed; state path moved.

Test plan

  • go build ./..., go vet ./... clean
  • go test ./... — all 141 packages pass
  • flux client/engine/ecosystem boundary guards pass
  • Golden help output regenerated and matching

- go.mod: github.com/GrayCodeAI/eyrie v0.6.0 -> github.com/GrayCodeAI/flux v0.0.1
- All import paths, type aliases (EyrieMessage -> FluxMessage etc.),
  internal identifiers, and import aliases renamed
- Env vars: EYRIE_CONFIG_DIR -> FLUX_CONFIG_DIR,
  EYRIE_MODEL_CATALOG_PATH -> FLUX_MODEL_CATALOG_PATH
- User state path: ~/.../eyrie/provider.json -> ~/.../flux/provider.json
- Boundary guards, ecosystem manifest, CI workflows, docs, golden help
  snapshots, and compatibility matrix all updated
- go.work workspace unaffected (module paths resolve via go.work)

BREAKING CHANGE: dependency module path changed; env vars renamed.
@Patel230
Patel230 merged commit 49baee5 into main Sep 15, 2026
25 checks passed
@Patel230
Patel230 deleted the chore/deps-flux-rename branch September 15, 2026 02:31
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