use celo verison of ganache (rather than random soloseng version)

[aaronmgdr]

Description

@soloseng noticed that monorepo was using wrong fork of ganache and fixed on monorepo celo-org/celo-monorepo#10917 this does the same here

Other changes

n/a

Tested

Related issues

• parrallel to fix ganache dependency resolution celo-monorepo#10917

Backwards compatibility

yep
Brief explanation of why these changes are/are not backwards compatible.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5b8a477

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@types/[email protected]	None	+1	1.77 MB	types
npm/[email protected]	None	0	541 kB	aearly
npm/[email protected]	filesystem Transitive: environment, shell	+48	3.18 MB	npm-cli-ops
npm/[email protected]	None	+8	2.72 MB	fanatid
npm/[email protected]	environment, filesystem	+5	289 kB	lukekarrys

🚮 Removed packages: npm/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note
Native code	npm/[email protected]	Location: Package overview

View full report↗︎

Next steps

What's wrong with native code?

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]