Merge branch 'main' into general-cleanup

Author: talentlessguy

.changeset/hot-spoons-sparkle.md

@@ -996,6 +996,14 @@ const communityPlugins: IPlugin[] = [
       "Hardhat plugin for enabling on-the-fly network switching within your Hardhat scripts and tasks",
     tags: ["Tasks", "Scripts", "Testing"],
   },
+  {
+    name: "@medga/hardhat-clone",
+    author: "The MEDGA Team",
+    authorUrl: "https://medga.org",
+    description:
+      "Clone an on-chain contract and integrate into your Hardhat project",
+    tags: ["etherscan", "clone", "verified contract"],
+  },
 ];
 
 const officialPlugins: IPlugin[] = [

docs/src/content/hardhat-runner/plugins/plugins.ts

@@ -40,6 +40,12 @@ An example file could be called `./ignition/parameters.json` and contain the fol
 }
 ```
 
+:::tip
+
+`JSON5` format is also supported for parameter files!
+
+:::
+
 This makes the `name` parameter for the `Apollo` module be `"Saturn V"`.
 
 To execute a deployment using parameters, you need to use the `--parameters` argument, like this:
@@ -74,6 +80,21 @@ To pass a `bigint` as a Module parameter, you can encode it as a string. Any str
 }
 ```
 
+You can also define global parameters that will be available to all modules. To do this, define a `$global` key in the parameters file:
+
+```json
+{
+  "$global": {
+    "shouldBeAllowed": true
+  },
+  "MyModule": {
+    "shouldBeAllowed": false
+  }
+}
+```
+
+In this example, the `shouldBeAllowed` parameter will be `true` for all modules except `MyModule`, where it will be `false`. Global parameters can be accessed in the same way as module parameters.
+
 ## Inspecting an existing deployment
 
 To get a list of all the deployment IDs that exist in the current project, run:

docs/src/content/ignition/docs/guides/deploy.md

@@ -1,5 +1,13 @@
 # hardhat
 
+## 2.22.13
+
+### Patch Changes
+
+- bf92f4c: Fixed more bugs in the newly ported Solidity tracing logic
+- 3df95d3: Remove support for `console.log` selectors that wrongly use "(u)int" type aliases in the selector calculation
+- 4c1bcfc: Fixed minor bugs in the newly ported Solidity tracing logic
+
 ## 2.22.12
 
 ### Patch Changes

packages/hardhat-core/CHANGELOG.md

@@ -1,6 +1,6 @@
 {
   "name": "hardhat",
-  "version": "2.22.12",
+  "version": "2.22.13",
   "author": "Nomic Labs LLC",
   "license": "MIT",
   "homepage": "https://hardhat.org",
@@ -100,7 +100,7 @@
   "dependencies": {
     "@ethersproject/abi": "^5.1.2",
     "@metamask/eth-sig-util": "^4.0.0",
-    "@nomicfoundation/edr": "^0.6.1",
+    "@nomicfoundation/edr": "^0.6.3",
     "@nomicfoundation/ethereumjs-common": "4.0.4",
     "@nomicfoundation/ethereumjs-tx": "5.0.4",
     "@nomicfoundation/ethereumjs-util": "9.0.4",

packages/hardhat-core/package.json

@@ -6,7 +6,7 @@ This plugin makes it easier to use Hardhat and [Foundry](https://getfoundry.sh/)
 
 When this plugin is enabled, Hardhat will use the same contracts directory that is used by Foundry, and it will be able to use dependencies installed with `forge install`.
 
-If you have a pure Hardhat project, your can use the `init-foundry` task to create a `foundry.toml` file. The file will be created using the proper values to make Foundry work well with your Hardhat project.
+If you have a pure Hardhat project, you can use the `init-foundry` task to create a `foundry.toml` file. The file will be created using the proper values to make Foundry work well with your Hardhat project.
 
 Read [our guide](https://hardhat.org/hardhat-runner/docs/advanced/hardhat-and-foundry) to learn more.
 

packages/hardhat-foundry/README.md

@@ -38,7 +38,7 @@ Install it, run `npx hardhat compile` and solc will compile the solpp generated
 
 ## Configuration
 
-This plugin can by configured by setting a `solpp` entry in `hardhat.config.js`. Its options are:
+This plugin can be configured by setting a `solpp` entry in `hardhat.config.js`. Its options are:
 
 - `defs`: is an object where each property is the symbol's name and its value is the actual definition. Definitions can be numbers, string, expressions, lists, or functions. For more detail about symbols you can check [solpp README](https://github.com/merklejerk/solpp).
 - `cwd: string`: directory where the contracts are located, it will be used for flattening purposes, by default it will be the project's source directory.