Skip to content

Commit a3b4ef9

Browse files
[CI] Update Foundry Upgrades plugin docs (#1135)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
1 parent 37d172c commit a3b4ef9

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

docs/modules/ROOT/pages/foundry/pages/foundry-upgrades.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -256,7 +256,7 @@ Upgrades.upgradeProxy(proxy, "MyContract.sol", "", opts);
256256
To enable code coverage reports with `forge coverage`, use the following deployment pattern in your tests: instantiate your implementation contracts directly and use the `UnsafeUpgrades` library. For example:
257257
```solidity
258258
address implementation = address(new MyContract());
259-
address proxy = Upgrades.deployUUPSProxy(
259+
address proxy = UnsafeUpgrades.deployUUPSProxy(
260260
implementation,
261261
abi.encodeCall(MyContract.initialize, ("arguments for the initialize function"))
262262
);
@@ -266,7 +266,7 @@ WARNING: `UnsafeUpgrades` is not recommended for use in Forge scripts. It does n
266266

267267
== Deploying and Verifying
268268

269-
Run your script with `forge script` to broadcast and deploy. See Foundry's https://book.getfoundry.sh/tutorials/solidity-scripting[Solidity Scripting] guide.
269+
Run your script with `forge script` to broadcast and deploy. See Foundry's https://book.getfoundry.sh/guides/scripting-with-solidity[Solidity Scripting] guide.
270270

271271
IMPORTANT: Include the `--sender <ADDRESS>` flag for the `forge script` command when performing upgrades, specifying an address that owns the proxy or proxy admin. Otherwise, `OwnableUnauthorizedAccount` errors will occur.
272272

0 commit comments

Comments
 (0)