Skip to content

Migrate to ops gen v2#2183

Draft
RensR wants to merge 2 commits into
mainfrom
ops-gen-v2
Draft

Migrate to ops gen v2#2183
RensR wants to merge 2 commits into
mainfrom
ops-gen-v2

Conversation

@RensR

@RensR RensR commented Jul 10, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

@RensR RensR force-pushed the ops-gen-v2 branch 6 times, most recently from 9d11352 to 30f637c Compare July 15, 2026 11:36
RensR added 2 commits July 15, 2026 13:51
fixup: convert remaining pre-existing v1_6_0/v2_0_0 fee & token adapter code to ops-gen v2 pattern

These files already existed on main (or were auto-merged in via rename
detection) using the old contract/operations.ExecuteOperation calling
convention, referencing types deleted by the migration. Converts them
to the same evmops.ExecuteRead/ExecuteWrite pattern used everywhere
else in this PR.
…nput

configure_token_for_transfers.go (added by the ops-gen v2 migration)
references input.LiquidityMigrationAmount, .LiquidityMigrationBasisPoints,
and .TimelockAddress to optionally trigger MigrateLockReleasePoolLiquidity
inline, but these fields were never added to the input struct in any of
the original commits. Adding them here, isolated for review, since this
completes a previously non-compiling feature rather than just resolving
a merge conflict.
@github-actions

Copy link
Copy Markdown
Metric ops-gen-v2 main
Coverage 69.6% 69.3%

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