chore: bump version for new release

[grasphoper]

No description provided.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub ↗.

	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@sentry/core@5.30.0
	@sentry/hub@5.30.0
	@sentry/minimal@5.30.0
	@sentry/tracing@5.30.0
	@sentry/types@5.30.0
	@sentry/utils@5.30.0
	@sinonjs/text-encoding@0.7.2
	@ungap/promise-all-settled@1.1.2
	buffer-writer@2.0.0
	babel-core@6.26.3
	@nomicfoundation/solidity-analyzer-darwin-arm64@0.1.0
	@nomicfoundation/solidity-analyzer-darwin-x64@0.1.0
	@nomicfoundation/solidity-analyzer-freebsd-x64@0.1.0
	@nomicfoundation/solidity-analyzer-linux-arm64-gnu@0.1.0
	@nomicfoundation/solidity-analyzer-linux-arm64-musl@0.1.0
	@nomicfoundation/solidity-analyzer-linux-x64-gnu@0.1.0
See 275 more rows in the dashboard ↗

View full report ↗

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub ↗.

Action	Severity	Alert (click for details)
Warn		@openzeppelin/contracts@4.1.0 has a Critical CVE. CVE: GHSA-5vp3-v4hc-gx76 UUPSUpgradeable vulnerability in @openzeppelin/contracts (CRITICAL) Affected versions: >= 4.1.0, < 4.3.2 Patched version: 4.3.2 Source: yarn.lock ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: 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@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@openzeppelin/contracts@4.1.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@openzeppelin/contracts@4.1.0 has a Critical CVE. CVE: GHSA-fg47-3c2x-m2wr TimelockController vulnerability in OpenZeppelin Contracts (CRITICAL) Affected versions: >= 4.0.0, < 4.3.1 Patched version: 4.3.1 Source: yarn.lock ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: 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@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@openzeppelin/contracts@4.1.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		babel-traverse@6.26.0 has a Critical CVE. CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: < 7.23.2 Patched version: No patched versions Source: yarn.lock ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: 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@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/babel-traverse@6.26.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report ↗