Closed renovate[bot] closed 7 months ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
nft-app | ❌ Failed (Inspect) | Jan 9, 2024 9:57pm |
Latest commit: 56b3a7c79bbc02121cbcfcde07282fbac1625d71
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
Updated dependencies detected. Learn more about Socket for GitHub ↗︎
Packages | Version | New capabilities | Transitives | Size | Publisher |
---|---|---|---|---|---|
@openzeppelin/hardhat-upgrades | 1.28.0...3.0.2 | None | +5/-2 |
4.53 MB | ericglau |
Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x
releases. But if you manually upgrade to 3.x
then Renovate will re-enable minor
and patch
updates automatically.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.
This PR contains the following updates:
1.28.0
->3.0.2
Release Notes
OpenZeppelin/openzeppelin-upgrades (@openzeppelin/hardhat-upgrades)
### [`v3.0.2`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%403.0.2) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@3.0.1...@openzeppelin/hardhat-upgrades@3.0.2) - Support proxy verification on Snowtrace. ([#954](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/954)) ### [`v3.0.1`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%403.0.1) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@3.0.0...@openzeppelin/hardhat-upgrades@3.0.1) - Update dependency on undici. ([#948](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/948)) - Update Defender SDK, support `txOverrides` option with Defender. ([#951](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/951)) ### [`v3.0.0`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%403.0.0) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@2.5.1...@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](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/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](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/937)) - **Note**: [Fully verifying proxies](https://docs.openzeppelin.com/upgrades-plugins/1.x/api-hardhat-upgrades#verify) 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](https://docs.openzeppelin.com/contracts/5.x/api/proxy). - `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`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%402.5.1) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@2.5.0...@openzeppelin/hardhat-upgrades@2.5.1) - Update Defender SDK, support `txOverrides` option with Defender. ([#951](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/951)) ### [`v2.5.0`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%402.5.0) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@2.4.3...@openzeppelin/hardhat-upgrades@2.5.0) - Add `defender.getDeployApprovalProcess` and `defender.getUpgradeApprovalProcess` functions. ([#934](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/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`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%402.4.3) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@2.4.2...@openzeppelin/hardhat-upgrades@2.4.3) - Bump dependency on `@openzeppelin/upgrades-core`. ([#930](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/930)) ### [`v2.4.2`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%402.4.2) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@2.4.1...@openzeppelin/hardhat-upgrades@2.4.2) - Fix `upgradeProxy` from an implementation that has a fallback function and is not using OpenZeppelin Contracts 5.0. ([#926](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/926)) ### [`v2.4.1`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%402.4.1) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@2.4.0...@openzeppelin/hardhat-upgrades@2.4.1) - Update Defender SDK. ([#924](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/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`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%402.4.0) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@2.3.3...@openzeppelin/hardhat-upgrades@2.4.0) - Add `createFactoryAddress` option for Defender deployments. ([#920](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/920)) **Note**: OpenZeppelin Defender deployments is in beta and its functionality is subject to change. ### [`v2.3.3`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%402.3.3) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@2.3.2...@openzeppelin/hardhat-upgrades@2.3.3) - Update OpenZeppelin Defender deployments to use Defender SDK. ([#888](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/issues/888)) ### [`v2.3.2`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%402.3.2) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@2.3.1...@openzeppelin/hardhat-upgrades@2.3.2) - Fix Hardhat compile error when using Solidity 0.5.x. ([#892](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/892)) ### [`v2.3.1`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%402.3.1) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@2.3.0...@openzeppelin/hardhat-upgrades@2.3.1) - Check for non-zero admin address when importing transparent proxy. ([#887](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/887)) ### [`v2.3.0`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%402.3.0) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@2.2.1...@openzeppelin/hardhat-upgrades@2.3.0) - Support new upgrade interface in OpenZeppelin Contracts 5.0. ([#883](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/883)) - Support importing and upgrading 5.0 proxies. - **Note**: Deploying 5.0 proxies is not supported yet. - Add validations for namespaced storage layout. ([#876](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/876)) ### [`v2.2.1`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%402.2.1) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@2.2.0...@openzeppelin/hardhat-upgrades@2.2.1) - Allow using proxy with different admin address than manifest. ([#859](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/859)) ### [`v2.2.0`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%402.2.0) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@2.1.1...@openzeppelin/hardhat-upgrades@2.2.0) - Rename Platform to Defender. ([#863](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/863)) **Note**: Functions that were for OpenZeppelin Platform have breaking changes since the previous release and have been renamed for OpenZeppelin Defender. See ([#863](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/863)) for details. OpenZeppelin Defender deployments is in beta and its functionality is subject to change. ### [`v2.1.1`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%402.1.1) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@2.1.0...@openzeppelin/hardhat-upgrades@2.1.1) - Use public Etherscan API from `hardhat-verify`. ([#857](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/857)) ### [`v2.1.0`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%402.1.0) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@2.0.2...@openzeppelin/hardhat-upgrades@2.1.0) - Add `txOverrides` option for overriding transaction parameters. ([#852](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/852)) ### [`v2.0.2`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%402.0.2) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@2.0.1...@openzeppelin/hardhat-upgrades@2.0.2) - Enable storage layout for overrides from Hardhat config. ([#851](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/851)) ### [`v2.0.1`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%402.0.1) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@2.0.0...@openzeppelin/hardhat-upgrades@2.0.1) - Update OpenZeppelin Platform client dependencies. ([#845](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/845)) ### [`v2.0.0`](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/releases/tag/%40openzeppelin/hardhat-upgrades%402.0.0) [Compare Source](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/compare/@openzeppelin/hardhat-upgrades@1.28.0...@openzeppelin/hardhat-upgrades@2.0.0) - Use `ethers` v6 and `hardhat-ethers` v3. ([#817](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/817)) - Use `hardhat-verify` for proxy verification. ([#829](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/829)) - Remove address override for deployments. ([#832](https://togithub.com/OpenZeppelin/openzeppelin-upgrades/pull/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](https://togithub.com/NomicFoundation/hardhat/releases/tag/%40nomicfoundation%2Fhardhat-toolbox%403.0.0).\ 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.
This PR has been generated by Mend Renovate. View repository job log here.