-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add warp config writer logic #511
Conversation
🦋 Changeset detectedLatest commit: e297125 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this PR not also contain the logic to fetch the warp deploy config so that we can ensure that the config is in sync with the monorepo getters?
should we first make the src-only changes in a PR, publish, update monorepo, and then add the exported configs in a separate PR? (or are we ok with that monorepo PR failing for now) |
+1 to separate logic from config changes if you don't mind |
This reverts commit 5b6f392.
### Description Adds existing warp route configs generated by infra Getters ### Backward compatibility Yes ### Testing <!-- Have any new metadata configs and deployment addresses been used with any Hyperlane tooling, such as the CLI? -->
This reverts commit 40108a7.
Description
Add warp config writer Registry logic
Generated by hyperlane-xyz/hyperlane-monorepo#5235
Backward compatibility
Yes
Fixes hyperlane-xyz/hyperlane-monorepo#5260