Deployment preparation: Protocol Fee Controller migration #189
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Deployment preparation: Protocol Fee Controller migration
Don't have a final commit; this is based off the protocol fee controller v2 deployment prep (unmerged). Just stacking them like this to get a full end-to-end to ensure everything will work.
This will need to be adjusted after merging the protocol fee controller task, so that the new fee controller can be deployed separately and passed in. Here, it is deployed along with the migrator, so that the fork test will work.
Deployment preparation tasks checklist:
README
is updated with the new task name and linkREADME
has a description and links to the artifactsbuild-info
is updated with artifacts compiled at the specified commitbuild-info
Code checklist:
master
, or there's a description of how to mergeIssue Resolution