openzeppelin-upgrades
openzeppelin-upgrades copied to clipboard
Plugins for Hardhat and Foundry to deploy and manage upgradeable contracts on Ethereum.
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [@ava/typescript](https://togithub.com/avajs/typescript) | [`^4.0.0` -> `^5.0.0`](https://renovatebot.com/diffs/npm/@ava%2ftypescript/4.1.0/5.0.0) | [](https://docs.renovatebot.com/merge-confidence/)...
[](https://renovatebot.com) This PR contains the following updates: | Update | Change | |---|---| | lockFileMaintenance | All locks refreshed | 🔧 This Pull Request updates lock files to use...
I have a deployment script that I've been using for the past six months or so to deploy and verify contracts on Polygon. Recently I've begun deploying on Base Sepolia,...
I'm using this package inside my `hardhat.config.ts` as: ```js import '@openzeppelin/hardhat-upgrades'; ``` Everything was working fine, but today, I added the support of zksolc compiler inside hardhat settings. The interesting...
> **Note:** This PR body was truncated due to platform limits. This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Adoption](https://docs.renovatebot.com/merge-confidence/) | [Passing](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) |...
For `defender.proposeUpgradeWithApproval`, the `approvalProcessId` option name is ambiguous. It is for customizing the upgrade approval process, not the deploy approval process. Consider renaming the option to `upgradeApprovalProcessId` and deprecating (but...
UpgradeableBeacon is incorrectly detected as an upgradable implementation because it has a function with signature `upgradeTo(address)`, which causes it to "look" like a UUPS implementation, even though this function is...
On https://docs.openzeppelin.com/upgrades-plugins/1.x/defender-deploy and https://docs.openzeppelin.com/upgrades-plugins/1.x/foundry-defender, clarify that the API key and secret referenced in the following statement is for the Production or Test Deploy Environment that was configured in Defender: ```...
Since release 1.13.2, with this [PR](https://github.com/OpenZeppelin/openzeppelin-upgrades/pull/926) we are getting this error while running `tsc` command: ``` node_modules/@openzeppelin/upgrades-core/dist/upgrade-interface-version.d.ts:1:23 - error TS2688: Cannot find type definition file for 'debug'. 1 /// ~~~~~...
It'd be great for the plugin to be able to verify in Sourcify the proxies/beacons it deploys.