Skip to content

chore: bump component versions#70

Merged
tmigone merged 3 commits into
mainfrom
tmigone/bump-versions
Apr 27, 2026
Merged

chore: bump component versions#70
tmigone merged 3 commits into
mainfrom
tmigone/bump-versions

Conversation

@tmigone
Copy link
Copy Markdown
Member

@tmigone tmigone commented Apr 21, 2026

No description provided.

tmigone added 2 commits April 17, 2026 17:55
Signed-off-by: Tomás Migone <tomas@edgeandnode.com>
Signed-off-by: Tomás Migone <tomas@edgeandnode.com>
@tmigone tmigone requested review from Maikol and RembrandtK April 21, 2026 20:56
Signed-off-by: Tomás Migone <tomas@edgeandnode.com>
@tmigone tmigone merged commit fb8cbc1 into main Apr 27, 2026
RembrandtK added a commit that referenced this pull request May 1, 2026
…ork subgraph

PR #70 ('chore: trim down config', 642978b) removed the LegacyServiceRegistry
and LegacyDisputeManager zero-address stubs that get jq'd into
addresses-local-network.json after the protocol deploy. The gateway side of
that change was clean — gateway no longer reads legacy_dispute_manager — but
the network subgraph (NETWORK_SUBGRAPH_COMMIT=5b6c22089) still references
both keys via subgraph.template.yaml / localNetworkAddressScript.ts. Without
the stubs those addresses come through mustache as empty strings and graph-cli
rejects the manifest with "Contract address is invalid", failing
subgraph-deploy and blocking docker compose up.

Restore the stubs as a minimal fix. The proper follow-up is bumping
NETWORK_SUBGRAPH_COMMIT to a version that drops the legacy data sources, but
that needs its own investigation.
@MoonBoi9001 MoonBoi9001 deleted the tmigone/bump-versions branch May 7, 2026 03:35
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.

2 participants