[Snyk] Upgrade @openzeppelin/merkle-tree from 1.0.7 to 1.0.8

[Dustin4444]

Snyk has created this PR to upgrade @openzeppelin/merkle-tree from 1.0.7 to 1.0.8.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 1 version ahead of your current version.

• The recommended version was released 8 months ago.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[gemini-code-assist]

Summary of Changes

Hello @Dustin4444, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request automates the process of keeping project dependencies current by upgrading @openzeppelin/merkle-tree to its latest patch version, 1.0.8. This minor update ensures the project benefits from the most recent fixes and improvements in the Merkle tree implementation, contributing to overall stability and security. The change also propagates necessary updates to several underlying cryptographic and utility libraries managed by pnpm.

Highlights

• Dependency Upgrade: The @openzeppelin/merkle-tree package has been upgraded from version 1.0.7 to 1.0.8.
• Transitive Dependency Updates: The pnpm-lock.yaml file reflects updates to several transitive dependencies, including new versions of @noble/ciphers, @noble/curves, @noble/hashes, @scure/base, @scure/bip32, @scure/bip39, and ethereum-cryptography, aligning with the new @openzeppelin/merkle-tree version.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snyk-upgrade-37bda63387e147fcca8261ea6a8fc5c5

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, upgrades the @openzeppelin/merkle-tree dependency from version 1.0.7 to 1.0.8. This is a patch update, which is generally safe and should not introduce breaking changes. The main change, besides the direct dependency version bump in package.json, is the update of transitive dependencies in pnpm-lock.yaml. Notably, version 1.0.8 of @openzeppelin/merkle-tree removes its dependency on @ethersproject/* packages (related to ethers v5) and instead uses @metamask/abi-utils and ethereum-cryptography. This appears to be a modernization step that aligns well with the project's use of ethers v6. The changes in package.json and pnpm-lock.yaml are consistent and correct for this upgrade. I see no issues with the changes themselves. Assuming CI tests pass, this PR is good to merge to keep dependencies up-to-date.