3 Commits
Author SHA1 Message Date
zeekayandHanzo Dev 9d4cc799a7 retire graph-node: the explorer bundles graph and indexer
luxfi/explorer carries luxfi/graph and luxfi/indexer, and every network's
exchange-api already reads it at /v1/graph/{slug}/{amm,dex}/graphql. A second
Graph Protocol stack -- graph-node, its postgres, its ipfs -- served nothing.

Removes its declarations, its repo entry, and two stale exchange-api
declarations that still named it: lux-explorer runs no exchange-api at all,
and lux-ns runs from deploy/, so applying either would have pointed a live
service at a service that no longer exists.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-17 12:05:41 -07:00
zeekayandHanzo Dev c61eaa4cc3 fix(repos): explore pins a tag that does not exist — v2.5.1 is v2.5.1-lux
REPOS.yaml is the manifest that replaced .gitmodules, and scripts/repos.sh
clones each repo at the pinned tag. Checked every pin against github:

    node        luxfi/node        v1.27.24      MISSING  (newest is v1.36.52)
    geth        luxfi/geth        v1.16.84      MISSING  (newest is v1.20.1)
    exchange    luxfi/exchange    web/5.141.1   MISSING  (tags are now v5.149.x;
                                                          the web/ prefix scheme
                                                          this note describes is
                                                          gone)
    explore     luxfi/explore     v2.5.1        MISSING  -> v2.5.1-lux
    graph-node  luxfi/graph-node  main          a branch, already flagged TODO
    evm, cli, netrunner, consensus, bridge, state          OK

Only explore is fixed here, because it is the one that is unambiguously a typo:
the tag exists, at the SAME version, with the `-lux` suffix this entry dropped.
Verified it resolves.

node, geth and exchange are NOT touched. Their pins are stale by many versions,
and choosing what universe builds and tests against is a release decision, not a
transcription fix — node alone would move v1.27 -> v1.36.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-02 07:06:32 -07:00
zeekay 44fd540f2e universe: drop submodule machinery — sibling clones + REPOS.yaml + semver pins
Replaces .gitmodules + git-submodule-based init/update/sync targets with
a manifest-driven sibling-clone model. No nested submodule checkouts
inside universe; each ecosystem repo lives at ~/work/lux/<name> as a
free-standing clone pinned to a semver tag (no main/latest/dev floating
tags in production).

- REPOS.yaml: source-of-truth manifest. 11 live repos pinned, 1
  (graph-node) still on main with TODO marker. 6 dead refs removed
  (explorer-lux, explorer-zoo, explore-lux, graph-node-lux, v2-subgraph,
  v3-subgraph — all 404 on github.com/luxfi; the explorer trio is
  folded into luxfi/explore which ships unified Next.js SPA + Go
  indexer).
- scripts/repos.sh {init|update|list}: reads REPOS.yaml via yq. init
  shallow-clones missing repos at the pinned tag. update fetches +
  checks out the pinned tag (optionally for a single repo via
  name=<repo>).
- Makefile: drops CORE/APP/DATA_SUBMODULES + ALL_SUBMODULES static
  lists. init/update/sync/list delegate to scripts/repos.sh. Section
  retitled 'Sibling Repos (REPOS.yaml — no submodules)'.
- .gitmodules: deleted (was empty 0-entry leftover).

To bump a pin: edit REPOS.yaml → make update name=<repo> → verify →
commit.
2026-06-10 09:04:04 -07:00