-
Notifications
You must be signed in to change notification settings - Fork 176
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
Upgrade core contracts #3733
Upgrade core contracts #3733
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3733 +/- ##
==========================================
- Coverage 55.50% 55.37% -0.13%
==========================================
Files 765 769 +4
Lines 69798 70257 +459
==========================================
+ Hits 38739 38906 +167
- Misses 27881 28163 +282
- Partials 3178 3188 +10
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
FVM Benchstat comparisonThis branch with compared with the base branch onflow:master commit b2dce40 The command Collapsed results for better readability
|
2a673aa
to
ae704df
Compare
I had to rollback some test changes made in #3473 due to the payer balance check change in onflow/flow-core-contracts#331 |
bors merge |
3770: Upgrade core contracts - port to v0.29 r=janezpodhostnik a=janezpodhostnik Port of #3733 to v0.29 This doesn't actually change anything for canary testnet or mainnet since the core contracts are already (or will be for mainnet) at the correct version. This does affect transient networks (most notably the emulator), due to a slightly different version of the contracts being deployed. Co-authored-by: Janez Podhostnik <[email protected]>
3770: Upgrade core contracts - port to v0.29 r=janezpodhostnik a=janezpodhostnik Port of #3733 to v0.29 This doesn't actually change anything for canary testnet or mainnet since the core contracts are already (or will be for mainnet) at the correct version. This does affect transient networks (most notably the emulator), due to a slightly different version of the contracts being deployed. Co-authored-by: Janez Podhostnik <[email protected]>
... to include: onflow/flow-core-contracts#331