Conversation
|
All alerts resolved. Learn more about Socket for GitHub. This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. Ignoring alerts on:
|
|
@SocketSecurity ignore npm/express-rate-limit@7.5.0 — only uses These two packages are only conditionally required if eslint is started with TL;DR: they added AI stuff to ESlint, but it will be removed again in future. |
27128df to
95c906a
Compare
|
✅ Previously successful run of [Test] PR Suite Web e2e tests workflow has been found. |
|
✅ Previously successful run of [Test] PR Suite Desktop e2e tests workflow has been found. |
| "@types/react": "18.2.55", | ||
| "bn.js": "5.2.1", | ||
| "bn.js": "5.2.2", | ||
| "bignumber.js": "9.3.0", |
There was a problem hiding this comment.
bn.js was pinned in #12133 to explicitly dedupe it even across major versions. Looking at yarn.lock, this is still relevant ✔️
Similar situation is now with bignumber.js:
Library @everstake/wallet-sdk@npm:1.0.15 requires exactly 9.1.2.
The changes from 9.1.2 to 9.3.0 are TS-only changes so let's deduplicate it too.
There was a problem hiding this comment.
Also why do we have two different BigNumber libraries? 🙈
Some legacy reasons as always, maybe they could be unified, but that's very very low priority 🧊
| pipe( | ||
| tokenAccounts, | ||
| A.sort((a, b) => new BigNumber(b.balance).comparedTo(new BigNumber(a.balance))), | ||
| A.sort((a, b) => new BigNumber(b.balance).comparedTo(new BigNumber(a.balance)) ?? 0), |
There was a problem hiding this comment.
BigNumber.comparedTo now returns null if any of the operands is NaN, which is not accepted by Array.sort.
I don't like this change; as per IEEE 754 NaN is a valid number, and all comparisons are false, so it shall not be sorted but stay in place.
→ I believe it's sensible to fallback to 0 in Array.sort, as it was before.
Maybe NaN can't even happen here, idk, but TS does not distinguish NaN from number (after all why should it, this makes sense)
The same applies to other similar diffs.
| "framer-motion": "^12.9.1", | ||
| "react": "18.2.0", | ||
| "react-hook-form": "^7.56.1", | ||
| "react-hook-form": "^7.56.3", |
There was a problem hiding this comment.
I tried reverting both fixes I made in #18677, because I've read the changes in the lib and it seemed related. But no, both fixes are still necessary.
| const config: webpack.Configuration = { | ||
| // Electron 35 runs on Chromium 134 https://www.electronjs.org/blog/electron-35-0#stack-changes | ||
| // Electron 36 runs on Chromium 136 https://www.electronjs.org/blog/electron-36-0#stack-changes | ||
| // but we are limited to 133 (supported by latest browserslist, as included by latest webpack) |
There was a problem hiding this comment.
I'll look into this when I get back to playing around with Electron Main ESM – I will bump webpack then.
95c906a to
b4905da
Compare
|
✅ Previously successful run of [Test] PR Suite Web e2e tests workflow has been found. |
|
✅ Previously successful run of [Test] PR Suite Desktop e2e tests workflow has been found. |
b4905da to
5ef376c
Compare
|
✅ Previously successful run of [Test] PR Suite Desktop e2e tests workflow has been found. |
|
✅ Previously successful run of [Test] PR Suite Web e2e tests workflow has been found. |
|
@SocketSecurity ignore-all |
|
Will merge despite failing Releases revision Checks |
Description
Update most Foundation-related dependencies.
major version:
electron(stack changes)globals(only for eslint)minimatch(node 20 requirement)minor version:
bignumber.js(TS-only changes)@eslint/jseslinteslinttypescript-eslintpatch version:
electron-builderelectron-updateridbreact-hook-formbn.jsnot updated:
tiny-secp256k1TODO in #12261electron-store + chalkTODO in #14482react-router + react-router-dom + historyTODO in #4649nxTODO in #18812ℹ️ For reference, last bump foundation deps PR was #18087 + #18682 + #18107 + #18704 + #18680
👁️ I skimmed through all code changes except eslint-related packages and
electron; found nothing suspicious ✅Related Issue
Resolve #18774
Dev QA
👁️ Besides CI checks, I have tested locally:
idb)idb)yarn refs&&yarn verify-project-referenceswork correctly (minimatch)yarn generate-packageworks correctly (sort-package-json)🔍🖥️ Suite web test results: View in Currents
🔍🖥️ Suite desktop test results: View in Currents
🔍🖥️ Suite native android test results: View in Currents