-
Notifications
You must be signed in to change notification settings - Fork 886
Bump goja version (CON-366) #3832
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -114,6 +114,8 @@ require ( | |
| github.com/ProtonMail/go-crypto v1.1.6 // indirect | ||
| github.com/cloudflare/circl v1.6.3 // indirect | ||
| github.com/cyphar/filepath-securejoin v0.4.1 // indirect | ||
| github.com/dlclark/regexp2/v2 v2.5.2 // indirect | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [suggestion] The |
||
| github.com/dop251/goja v0.0.0-20260723142020-b4aef50fa347 // indirect | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [suggestion] Worth stating the actual driver for this bump in the PR description. "current module proxy If this is a CVE/security fix, say so — that justifies the override. If it's routine freshening, consider instead bumping goja inside the sei go-ethereum fork so the change is covered by that repo's tests, or pinning to a tagged goja release rather than an untagged pseudo-version. Either way, recording the reason here or in the commit message keeps a future |
||
| github.com/emirpasic/gods v1.18.1 // indirect | ||
| github.com/go-git/gcfg v1.5.1-0.20230307220236-3a3c6141e376 // indirect | ||
| github.com/go-git/go-billy/v5 v5.8.0 // indirect | ||
|
|
@@ -172,11 +174,9 @@ require ( | |
| github.com/desertbit/timer v0.0.0-20180107155436-c41aec40b27f // indirect | ||
| github.com/dgraph-io/badger/v3 v3.2103.2 // indirect | ||
| github.com/dgraph-io/ristretto v0.2.0 // indirect | ||
| github.com/dlclark/regexp2 v1.7.0 // indirect | ||
| github.com/docker/cli v24.0.7+incompatible // indirect | ||
| github.com/docker/go-connections v0.4.0 // indirect | ||
| github.com/docker/go-units v0.5.0 // indirect | ||
| github.com/dop251/goja v0.0.0-20230605162241-28ee0ee714f3 // indirect | ||
| github.com/dustin/go-humanize v1.0.1 // indirect | ||
| github.com/ethereum/c-kzg-4844 v1.0.0 // indirect | ||
| github.com/ethereum/go-verkle v0.2.2 // indirect | ||
|
|
||
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.
[nit] The graph now carries two majors of the same regex engine:
regexp2/v2 v2.5.2(new goja) alongsideregexp2 v1.7.0(line 177, still pulled by other deps). That's expected for a v2 module path, not a bug — just worth a sanity check that nothing else in the tree was relying on goja and v1 regexp2 sharing state/behavior, and that the extra copy in the binary is acceptable.