Skip to content

Feat/registry#1

Merged
julienh-ssv merged 1 commit intostagefrom
feat/registry
Oct 16, 2025
Merged

Feat/registry#1
julienh-ssv merged 1 commit intostagefrom
feat/registry

Conversation

@julienh-ssv
Copy link
Copy Markdown

@julienh-ssv julienh-ssv commented Oct 16, 2025

This PR is a proof of concept wiring of our new compose-registry:

Feature:

  • Mailboxes are fetched from the new registry
  • A new optional flag is added to allow selecting the registry path (only useful for local dev environments, by default embedded registry is used)

@julienh-ssv julienh-ssv self-assigned this Oct 16, 2025
@julienh-ssv julienh-ssv force-pushed the feat/registry branch 2 times, most recently from 0602a3a to 208abcc Compare October 16, 2025 07:57
@zktaiga zktaiga requested review from kchojn and zktaiga October 16, 2025 08:17
@kchojn
Copy link
Copy Markdown

kchojn commented Oct 16, 2025

I think this is the wrong place for PR
op-geth is expected to be mostly supported by the SDK Publisher, so the whole registry part should be:

  • moved to compose-publisher/publisher
    OR
  • in a very minimal version in op-geth; now I see several public utils, so shouldnt they be made available via registry?

@julienh-ssv julienh-ssv merged commit 93d2e25 into stage Oct 16, 2025
@julienh-ssv julienh-ssv deleted the feat/registry branch October 16, 2025 11:05
julienh-ssv added a commit that referenced this pull request Nov 17, 2025
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