-
Notifications
You must be signed in to change notification settings - Fork 474
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
Feat: upgrade to 1.4.1 #4645
Feat: upgrade to 1.4.1 #4645
Conversation
Branch preview✅ Deploy successful! Website: Storybook: |
📦 Next.js Bundle Analysis for safe-wallet-webThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
Page | Size (compressed) |
---|---|
global |
1011.77 KB (🟡 +430 B) |
Details
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script>
tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
Thirteen Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
Page | Size (compressed) | First Load |
---|---|---|
/apps |
33.79 KB (🟡 +4.06 KB) |
1.02 MB |
/apps/custom |
31.85 KB (🟡 +4.06 KB) |
1.02 MB |
/apps/open |
54.18 KB (🟡 +4.06 KB) |
1.04 MB |
/home |
59.26 KB (🟡 +4.07 KB) |
1.05 MB |
/settings/safe-apps |
18.36 KB (🔴 +4.06 KB) |
1.01 MB |
/settings/setup |
30.81 KB (🟡 +1 B) |
1.02 MB |
/swap |
752 B (🟡 +3 B) |
1012.5 KB |
/transactions |
97.2 KB (🟡 +4.06 KB) |
1.08 MB |
/transactions/history |
97.17 KB (🟡 +4.06 KB) |
1.08 MB |
/transactions/messages |
58.95 KB (🟡 +4.06 KB) |
1.05 MB |
/transactions/msg |
55.11 KB (🟡 +4.06 KB) |
1.04 MB |
/transactions/queue |
48.06 KB (🟡 +4.06 KB) |
1.03 MB |
/transactions/tx |
47.32 KB (🟡 +4.06 KB) |
1.03 MB |
Details
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link
is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script>
tag are not accounted for in this analysis
Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.
Coverage reportCaution Test run failed
Show new covered files 🐣
Show files with reduced coverage 🔻
Test suite run failedFailed tests: 0/1672. Failed suites: 6/237.
Report generated by 🧪jest coverage report action from e452768 |
src/services/tx/safeUpdateParams.ts
Outdated
@@ -32,6 +34,10 @@ const getChangeFallbackHandlerCallData = async ( | |||
export const createUpdateSafeTxs = async (safe: SafeInfo, chain: ChainInfo): Promise<MetaTransactionData[]> => { | |||
assertValidSafeVersion(safe.version) | |||
|
|||
if (semverSatisfies(safe.version, '>=1.3.0')) { |
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.
Are we sure this will also work with future safe version e.g. going from 1.4.1 to 1.5.0? Otherwise I would limit it to only target 1.3.0 versions instead of >=1.3.0
@@ -71,7 +70,7 @@ export const isRouteEnabled = (route: string, chain?: ChainInfo) => { | |||
} | |||
|
|||
export const getLatestSafeVersion = (chain: ChainInfo | undefined): SafeVersion => { | |||
const latestSafeVersion = chain && hasFeature(chain, FEATURES.SAFE_141) ? LATEST_SAFE_VERSION : FALLBACK_SAFE_VERSION | |||
const latestSafeVersion = chain?.recommendedMasterCopyVersion || LATEST_SAFE_VERSION |
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.
What if a network doesn't have 1.4.1? Previously we would use FALLBACK_SAFE_VERSION
which defaulted to 1.3.0 but now this won't be the case anymore.
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.
It will fail somewhere down the line where it gets an actual deployment. 1.3.0 is also not guaranteed to exist on all chains.
What it solves
This PR contains the changes from #4642
SAFE_141
feature toggle, use therecommendedMasterCopyVersion
field fromChainInfo
1.3.0 Safes:
1.1.1 Safes:
How to test
Case 1:
Case 2:
Case 3: