-
Notifications
You must be signed in to change notification settings - Fork 49
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
chore: prepare v4.0.0-rc0
#255
Conversation
}, | ||
{ | ||
upgradeName: "argon", | ||
image: nobleImageInfo[0], | ||
// postUpgrade: testPostArgonUpgradeMainnet, | ||
postUpgrade: testPostArgonUpgrade, |
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.
Unfortunately, we are going to have to remove the post-upgrade part from the mainnet upgrade test if we want this to pass.
This is because of the way we created the fiat-tokenfactory where you must have an owner in state. IE, we hard coded the owner role in the neon
upgrade handler.
The reason this works in the testnet upgrade test is because we altered the fiat-tokenfactory owner in this image of noble:
https://github.com/strangelove-ventures/noble/blob/72e36f89a65376d40a339cb9cf8b99fc461628cf/interchaintest/upgrade_grand-1_test.go#L25
The owner in the image above, matches the owner here:
https://github.com/strangelove-ventures/noble/blob/72e36f89a65376d40a339cb9cf8b99fc461628cf/interchaintest/upgrade_argon_test.go#L38
No description provided.