chore(deps): update dependency @openzeppelin/hardhat-upgrades to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@openzeppelin/hardhat-upgrades (source)	1.28.0 -> 3.2.0

---

Release Notes

OpenZeppelin/openzeppelin-upgrades (@​openzeppelin/hardhat-upgrades)

v3.2.0

Compare Source

• Breaking change: Remove defender.proposeUpgrade from Defender legacy. Defender users should use defender.proposeUpgradeWithApproval instead. (#​1041)

v3.1.1

Compare Source

• Defender: Fix proxy deployments when using constructorArgs option, support arbitrary constructor arguments. (#​1029)

v3.1.0

Compare Source

• Defender: Fix handling of license types for block explorer verification, support licenseType and skipLicenseType options. (#​1013)

Breaking changes

• When deploying through Defender, if your contract does not have an SPDX license identifier, the verified source code on Etherscan will no longer show any license type.
  • If you want the license type to appear as "None", either set your contract to have // SPDX-License-Identifier: UNLICENSED according to Solidity docs, or set the licenseType option to "None".

v3.0.5

Compare Source

• Simplify console logging for admin.transferProxyAdminOwnership. (#​978)
• Support private networks and forked networks with Defender. (#​989)

v3.0.4

Compare Source

• Support externally linked libraries for Defender deployments. (#​960)

v3.0.3

Compare Source

• Support Defender deployments using EOA or Safe. (#​967)

v3.0.2

Compare Source

• Support proxy verification on Snowtrace. (#​954)

v3.0.1

Compare Source

• Update dependency on undici. (#​948)
• Update Defender SDK, support txOverrides option with Defender. (#​951)

v3.0.0

Compare Source

• Deploy proxies from OpenZeppelin Contracts 5.0. (#​919)
• Support initialOwner option when deploying a transparent proxy or beacon. If not set, the externally owned account used during deployment will be the default owner for the transparent proxy's admin or the beacon, respectively.
• Update optional peer dependency on @nomicfoundation/hardhat-verify to v2.0.0 or higher. (#​937)
  • Note: Fully verifying proxies is only supported with Etherscan at the moment. The Hardhat Upgrades plugin does not currently assist with Sourcify verification for proxies.

Breaking changes

• deployProxy, deployBeacon, deployBeaconProxy: Deploys proxy contracts from OpenZeppelin Contracts 5.0.
• deployProxy:
  • Deploying a transparent proxy automatically causes a new proxy admin contract to be deployed along with the proxy.
  • New transparent proxy deployments no longer use an existing proxy admin, even if one was previously recorded in the network file.
  • New proxy admins are no longer recorded in the network file.
• deployProxyAdmin: Removed, since proxy admins are deployed automatically by transparent proxies.
• admin.changeProxyAdmin: Not supported with admins or proxies from OpenZeppelin Contracts 5.0. Only supported for previously deployed admins and proxies from OpenZeppelin Contracts 4.x or below.
• admin.transferProxyAdminOwnership: This function no longer uses the proxy admin from the network file. It now requires a proxyAddress argument to be passed in.
• @nomicfoundation/hardhat-verify v1.x and @nomicfoundation/hardhat-toolbox v3.x are no longer supported with this plugin. If you are using these packages, update them to @nomicfoundation/hardhat-verify v2.x and @nomicfoundation/hardhat-toolbox v4.x.

v2.5.1

Compare Source

• Update Defender SDK, support txOverrides option with Defender. (#​951)

v2.5.0

Compare Source

• Add defender.getDeployApprovalProcess and defender.getUpgradeApprovalProcess functions. (#​934)
• Deprecate defender.getDefaultApprovalProcess function. This function is equivalent to defender.getUpgradeApprovalProcess.

Note: OpenZeppelin Defender deployments is in beta and its functionality is subject to change.

v2.4.3

Compare Source

• Bump dependency on @openzeppelin/upgrades-core. (#​930)

v2.4.2

Compare Source

• Fix upgradeProxy from an implementation that has a fallback function and is not using OpenZeppelin Contracts 5.0. (#​926)

v2.4.1

Compare Source

• Update Defender SDK. (#​924)
• Throw error if not using a relayer for deployments, until other types of deployments are supported.

Note: OpenZeppelin Defender deployments is in beta and its functionality is subject to change.

v2.4.0

Compare Source

• Add createFactoryAddress option for Defender deployments. (#​920)

Note: OpenZeppelin Defender deployments is in beta and its functionality is subject to change.

v2.3.3

Compare Source

• Update OpenZeppelin Defender deployments to use Defender SDK (#​888)

v2.3.2

Compare Source

• Fix Hardhat compile error when using Solidity 0.5.x. (#​892)

v2.3.1

Compare Source

• Check for non-zero admin address when importing transparent proxy. (#​887)

v2.3.0

Compare Source

• Support new upgrade interface in OpenZeppelin Contracts 5.0. (#​883)
• Support importing and upgrading 5.0 proxies.
  • Note: Deploying 5.0 proxies is not supported yet.
• Add validations for namespaced storage layout. (#​876)

v2.2.1

Compare Source

• Allow using proxy with different admin address than manifest. (#​859)

v2.2.0

Compare Source

• Rename Platform to Defender. (#​863)

Note: Functions that were for OpenZeppelin Platform have breaking changes since the previous release and have been renamed for OpenZeppelin Defender. See (#​863) for details. OpenZeppelin Defender deployments is in beta and its functionality is subject to change.

v2.1.1

Compare Source

• Use public Etherscan API from hardhat-verify. (#​857)

v2.1.0

Compare Source

• Add txOverrides option for overriding transaction parameters. (#​852)

v2.0.2

Compare Source

• Enable storage layout for overrides from Hardhat config. (#​851)

v2.0.1

Compare Source

• Update OpenZeppelin Platform client dependencies. (#​845)

v2.0.0

Compare Source

• Use ethers v6 and hardhat-ethers v3. (#​817)
• Use hardhat-verify for proxy verification. (#​829)
• Remove address override for deployments. (#​832)

Breaking changes

This new major version requires ethers v6 and @nomicfoundation/hardhat-ethers v3 as peer dependencies.
For Etherscan verification, it also requires @nomicfoundation/hardhat-verify.

How to update from a previous version

Update your existing project according to Hardhat Toolbox v3's release notes.
Then update this plugin, for example: npm install @​openzeppelin/hardhat-upgrades@latest

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: e54c5c8

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.

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
dapp-token-ico	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 22, 2024 4:15am

[sweep-ai]

Apply Sweep Rules to your PR?

• Apply: All new business logic should have corresponding unit tests.
• Apply: Refactor large functions to be more modular.
• Apply: Add docstrings to all functions and file headers.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@openzeppelin/defender-sdk-base-client@1.14.1	None	0	76.7 kB	tirumerla
npm/@openzeppelin/defender-sdk-deploy-client@1.14.1	environment	0	69 kB	tirumerla
npm/@openzeppelin/defender-sdk-network-client@1.14.1	environment	0	45.5 kB	tirumerla
npm/@openzeppelin/hardhat-upgrades@3.2.0	filesystem	0	401 kB	ericglau

🚮 Removed packages: npm/@ethersproject/sha2@5.7.0, npm/@openzeppelin/defender-base-client@1.54.6, npm/@openzeppelin/hardhat-upgrades@1.28.0, npm/@openzeppelin/platform-deploy-client@0.8.0

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report↗︎

[coderabbitai]

Important

Review skipped

Bot user detected.

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.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.