Skip to content
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

Migration Contracts Changes #777

Merged
merged 7 commits into from
Sep 18, 2024
Merged

Migration Contracts Changes #777

merged 7 commits into from
Sep 18, 2024

Conversation

remedcu
Copy link
Member

@remedcu remedcu commented Sep 12, 2024

This PR adds the new Safe Migration Contracts to the deployments of v1.4.1. Corresponding changes have been made to the automated tests and reviews as well.

@remedcu remedcu self-assigned this Sep 12, 2024
@remedcu remedcu requested review from gjeanmart and a team as code owners September 12, 2024 14:16
scripts/review/diff.ts Outdated Show resolved Hide resolved
@remedcu remedcu requested a review from mmv08 September 13, 2024 08:41
Copy link
Collaborator

@nlordell nlordell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some more changes, and CI looks to be failing.

scripts/review/diff.ts Outdated Show resolved Hide resolved
scripts/review/diff.ts Outdated Show resolved Hide resolved
@remedcu
Copy link
Member Author

remedcu commented Sep 16, 2024

Some more changes, and CI looks to be failing.

CI will fail because we are changing the asset but not adding a new chain ID or deployments.

@@ -115,6 +118,41 @@ describe('assets/', () => {
}
});

it('should contain the migration contracts networks in all other files', async () => {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO this can be part of the above test, most of the counting is duplicated anyway.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I initially thought so, but as the intention of the tests were different, thought to have it separated (one to make sure all the deployments are present in all contracts except the migration one, while the other test makes sure the migration test deployments are also present in other contracts.)

scripts/review/diff.ts Outdated Show resolved Hide resolved
@remedcu remedcu merged commit b990639 into main Sep 18, 2024
1 of 2 checks passed
@remedcu remedcu deleted the migration-contracts branch September 18, 2024 08:24
remedcu added a commit that referenced this pull request Sep 25, 2024
Safe deployments for the migration contracts were added in #777 but
retrieving those deployments was not added. This PR adds the same.
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.

3 participants