dependabot-npm(deps-dev): bump @openzeppelin/hardhat-upgrades from 2.5.1 to 3.0.5

[dependabot]

Bumps @openzeppelin/hardhat-upgrades from 2.5.1 to 3.0.5.

Release notes

Sourced from @​openzeppelin/hardhat-upgrades's releases.

@​openzeppelin/hardhat-upgrades@​3.0.5

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

@​openzeppelin/hardhat-upgrades@​3.0.4

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

@​openzeppelin/hardhat-upgrades@​3.0.3

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

@​openzeppelin/hardhat-upgrades@​3.0.2

• Support proxy verification on Snowtrace. (#954)

@​openzeppelin/hardhat-upgrades@​3.0.1

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

@​openzeppelin/hardhat-upgrades@​3.0.0

This is a major version of the Hardhat Upgrades plugin that contains breaking changes. Please review the changes below.

This version deploys proxy contracts from OpenZeppelin Contracts 5.0, and no longer supports deploying proxy contracts from OpenZeppelin Contracts 4.x. However, it still supports importing and/or managing existing proxies that were deployed from previous versions.

If you are using Hardhat Verify, this plugin now requires Hardhat Verify 2.0.0 or higher.

Summary

• 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.

@​openzeppelin/hardhat-upgrades@​3.0.0-alpha.0

Disclaimer

This is an alpha release of a new major version which contains breaking changes. Additional breaking changes may be introduced leading up to the full release.

Documentation

API documentation for this alpha release can be found here.

Summary

• Deploy proxies from OpenZeppelin Contracts 5.0.

... (truncated)

Commits

• 6869419 Support private networks and forked networks with Defender (#989)
• 3960e8f Remove console logging for transferProxyAdminOwnership (#978)
• 0f8e5e5 Update devDependencies for OpenZeppelin Contracts 5.0.2 (#986)
• 5785b3f Update dependency ava to v6 (#935)
• 0f0004e Update dependency undici to v6 (#949)
• 76e39a8 Update lockfile (#982)
• ad24a72 Update dependency typescript to v5 (#760)
• f23e837 Update linters to v7 (major) (#971)
• fa9d655 Update to Node 18 (#911)
• 5c6829b Support externally linked libraries for Defender deployments (#960)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

The following labels could not be found: dependencies.

[github-actions]

This pull request is stale because it has been open for 14 days with no activity.
It will be closed in 7 days unless the stale label is removed.

[github-actions]

This pull request was closed due to a lack of activity for 7 days after it was stale.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.