-
Notifications
You must be signed in to change notification settings - Fork 45
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
Deployment preparation: Stable Pool V2 #212
base: master
Are you sure you want to change the base?
Conversation
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.
LGTM!
@@ -7,7 +7,7 @@ import { ONES_BYTES32, ZERO_ADDRESS } from '@helpers/constants'; | |||
import { bn, fp } from '@helpers/numbers'; | |||
import { StablePoolDeployment } from '../input'; | |||
|
|||
describeForkTest('StablePool-V3', 'mainnet', 21336200, function () { | |||
describeForkTest.skip('StablePool-V3', 'mainnet', 21336200, function () { |
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.
Nice to know that we need to actively skip the tests inside the deprecated folder. I wonder if there's a way to automatically ignore these tests.
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.
We'd have to special-case it in the scripts, which we generalized to find everything (making other things easier). It's possible, but since deprecation isn't that common, maybe it's not too onerous. (Come to think of it, we should probably add that to the deprecation checklist then, which we just changed.)
Technically they should all still work; I believe we skip them mainly to save CI time.
# Conflicts: # CHANGELOG.md # README.md
Deployment preparation: Stable Pool V2
Deploy V2 of the Stable Pool, which raises the amp factor limit and allows the swap fee manager to change the amp factor without governance intervention.
build-info: balancer/balancer-v3-monorepo@e1ae7f0
Note that the readme issue with the Cow Fee Burner in the wrong place is addressed in PR #210.
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
Deprecating old tasks checklist:
deprecated/
directoryREADME
is updated: old task is moved to the 'deprecated' section, and links are updated with thedeprecated/
prefixindex.ts
,input.ts
and fork tests are updatedREADME
is updated with a warning sign, a link to the replacement task and a short descriptionCode checklist:
master
, or there's a description of how to mergeIssue Resolution
Closes #184